Using weblogic clustering to improve permance in J2EE applications

I'm wondering if someone can help me to figure out a solution to some performance issues already existing in my Weblogic-based application.
          - Current configuration: 2 weblogic domains where each domain contains it's own weblogic instance and each instance is running different applications and all running in the same computer. I'm not using clustering.
          Configuration described above have performance issues, so I would like to receive tipical recommendations to improve performance including a change of the configuration of weblogic servers. One of my ideas is to use clustering as follows:
          Have each J2EE app described above running on their own computer, where each computer includes one weblogic domain with two instances of the same application with clustering enabled for fail-over and load-balancing. This idea is makes some sense, or I'm suggesting a very bad idea ?
          thanks for your help

I'd first need to understand what is causing the performance issues. ie what is the factor limiting your performance? Are you at 100% CPU? Are you waiting for a database to respond etc? Once we have that analysis, we can probably give you better advice on how to fix it.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Similar Messages

Special consideration for coding clients while using weblogic clustering

          Hi.
          I wanted to know whether there are any special consdirations to
          be taken while coding clients(servlets in our case) for EJBs when
          we are using clustering of App servers.
          In our setup, we are following the recommended 2-tier architecture
          for Weblogic5.1
          thanks and regards,
          Amol


Amol wrote:
          > Hi,
          > adding a couple of points to the previous mail:
          > 1. In case of servlet failure after doXXX() method has been
          > called and before the method returns, if the app server
          > fails, will doXXX() be called again on the servlet in the
          > secondary server?
          > 2. How much time does it take for the servlet session on
          > one machine to be replicated on the second machine when
          > using in-memory replication.
          It depends on the size of the object and complexity.
          -- Prasad
          >
          > Thanks,
          > Amol
          >
          > "Amol" <[email protected]> wrote:
          > >
          > >Hi kumar (and everybody),
          > >
          > >Your opinion resolves the doubt i had in mind, since even
          > >WebLogic
          > >docs do not say anything about clustering affecting the
          > >coding
          > >of bean clients.
          > >
          > >However may I request you to please evaluate the same
          > >query with
          > >respect to the following conditions:
          > >1. The Session bean calls a stored proc on the db. After
          > >the call
          > >to stored proc and before the stored proc returns with
          > >the results,
          > >the app server fails.
          > >Here there could be two cases of interest, a) Stored proc
          > >does
          > >a write on db -OR- b) Stored proc does only a read on
          > >db
          > >2. The Session bean calls an Entity bean which "writes"
          > >to the
          > >db. The db write is successful, but before the entire
          > >call to the
          > >session bean is completed(that is before user gets his
          > >results)
          > >the Server fails. Now permanent changes have been made
          > >to the db,
          > >but client doesnt get the results.
          > >
          > >Please note the fact that we are using recommended 2-tier
          > >architecture
          > >and in this case server failure would imply failure of
          > >Servlet
          > >as well as the beans.
          > >
          > >Regards,
          > >Amol
          > >--------------------------
          > >
          > >Kumar Allamraju <[email protected]> wrote:
          > >>Absolutely not. Make sure the objects you are putting
          > >>in the session are
          > >>serializable.
          > >>
          > >>
          > >>
          > >>Amol wrote:
          > >>
          > >>> Hi.
          > >>> I wanted to know whether there are any special consdirations
          > >>to
          > >>> be taken while coding clients(servlets in our case)
          > >>for EJBs when
          > >>> we are using clustering of App servers.
          > >>>
          > >>> In our setup, we are following the recommended 2-tier
          > >>architecture
          > >>> for Weblogic5.1
          > >>>
          > >>> thanks and regards,
          > >>> Amol
          > >>
          > >
          Cheers
          - Prasad

How can I mapping directory by using Weblogic Server?

Hi,
We used to use iPlant as the web server. How can mapping directory using Weblogic
server?
$PATH=$wl_home/config/epdm/applications/DefaultWebApp/WEB-INF/classes
such as to map the following:
From To
/rok/servlet $PATH/servlet-dev/WEB-INF/classes
/rok/imagest $PATH/servlet-dev/images
/rok/html $PATH/servlet-dev/htm
/servlet $PATH/servlet-dev/servlet
Thanks!
Hanqing

Use JMX. See http://dima.dhs.org.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Nicole" <[email protected]> wrote in message
news:3c4d6daa$[email protected]..
>
Hi all,
in my EJBs I want to know, on which server instance I´m running. I needthis for
logging info. How can I get the servers name?
When I load the JNDI tree and select java:comp, an error occurs and a lotof information
is printed. One is weblogic.Server and that is what I´m searching for.
I use WLS 6.1 SP1
Any ideas? Thanks,
Nicole

Migrating CORBA apps to J2EE using Weblogic

Hullo,
This may not be directly related to RMI-IIOP per se, but I was hoping to ask for
some best practices / pointers / risks involved in migrating a CORBA app to a
J2EE environment.
I understand that a lot depends on the application semantics itself (sessions
/ transactions / security / ..) but I was hoping to ask for some general rules
of thumb.
The business domain is well identified - only a new technology needs to be incorporated.
We are going to take on this task using Weblogic 6.1 sp2 and realize that a phased
process would be ideal where critical parts of the application are kept intact
as CORBA components and the rest are rewritten as J2EE components talking to the
legacy components using Java interfaces generated by the IDL.
Any experiences and stories would be most appreciated.
Cheers!
Ajay

Hullo,
This may not be directly related to RMI-IIOP per se, but I was hoping to ask for
some best practices / pointers / risks involved in migrating a CORBA app to a
J2EE environment.
I understand that a lot depends on the application semantics itself (sessions
/ transactions / security / ..) but I was hoping to ask for some general rules
of thumb.
The business domain is well identified - only a new technology needs to be incorporated.
We are going to take on this task using Weblogic 6.1 sp2 and realize that a phased
process would be ideal where critical parts of the application are kept intact
as CORBA components and the rest are rewritten as J2EE components talking to the
legacy components using Java interfaces generated by the IDL.
Any experiences and stories would be most appreciated.
Cheers!
Ajay

Calrification for Weblogic Clustering

Our J2EE application is multitiered where JSPs&Servlets(Frontend) runs in a weblogic instance and EJBs(Backend) runs in two weblogic instances which are clustered. Here the Frontend weblogic instance and one of the clustered Backend weblogic instance are running in a same machine A and the other clustered Backend weblogic instance is running in another machine B. We had tested the following cases for Failover
Note :
please consider "JSPs&Servlets" as Frontend and "EJBs" as Backend.
Weblogic 9.2 and stateless session beans are used.
Frontend is not clustered.
Case 1:
We are doing a transaction where the request from frontend goes to one of the of the Clustered Backend weblogic instance. Before the transaction gets completed this backend weblogic instance is made to shutdown. The transaction has failed over to the another available Clustered Backend weblogic instance . The transaction had completed successfully and the Failover is working fine.
Case 2:
We are doing a transaction where the request from frontend(running in Machine A) goes to the Clustered Backend weblogic instance running in the Machine A itself. Before the transaction gets completed, the machine A is made to shutdown (i.e. both frontend and backend weblogic instance shuts down at the same time). Here the transaction has failed and could not able failover to the other available Backend weblogic instance .
Please clarify whether weblogic cluster supports the Backend failover when both the Frontend and Backend are brought down at the same time?
Any weblogic CLustering experts, please clarify...

Hi Jayesh,
Thanks very much for your reply.
I understood that your reply "You might want to consider collapsing front end (servlet & JSP) and back end (EJB) servers into a single WebLogic server for better fail over support." means that JSP&Servlet and EJB should be combined to form a single archive(EAR) which has to be deployed in single weblogic instance.
Please check whether my assumptions are correct for your suggestion on better failover.
1.The cluster configuration of JSPs&Servlet(web.xml) and EJBs(ejb-jar.xml) running in single weblogic instance will be similar to the cluster configuration of JSPs&Servlet(web.xml) and EJBs(ejb-jar.xml) running in separate weblogic instances. i.e All the configurations are same, but instead of the application running in separate weblogic instances, it will run in single weblogic instance.
2.In the URL for specifying the EJB connection from the JSP&Servlet, the cluster IP address should be used.
You have mentioned that if EJB client is not alive, the failover will not work. Please clarify how the failover will work in this case only(JSP&Servlet and EJB running in single weblogic instance and clustered).
Thanks,
Thiyagu

Porting j2ee application from Weblogic to Oracle 10g AS

What are the common guidelines/consideration when we port a J2EE application on Oracle Application server 10g. from WebLogic 8.1. If you have some inputs on pin points/guidelines/Architecture decisions that we might need to consider when we port a J2EE application on different J2EE application server
I got the link for app server migration but it is broken :
http://www.oracle.com/consulting/technology/appserver_migration_ds.pdf
Our application uses the following J2EE components
1. JDBC 2.0
2. JNDI
3. DAO
4. EJB
5. JMS
6. JAAS
7. JAVA Mails.
8. Servlets, JSP’s
I can think following point that needs to take care while porting
1. Its deployment configuration vis-a-vis the apps on top
2. The APIs it exposes (actually the information it allows the apps to pass in to the framework
3. The data it encapsulates (in order to be app-server agnostic; does it need to be now exposed to apps?)
Some J2EE specific areas
1. JNDI usage and exposure to apps 2. Properties files/XML files
2. Location specification 3. Resource bundle location specification
4. EJB deployment descriptors
5. Class/jar references between wars and ears
6. Jar sharing model across ears
7. Class loader differences across app-servers
8. JMS settings (queues, topics, factories, durability etc)
9. UI tags 10. Startup services
11. Managed services (JMX)
12. Security context passing
13. Clustered configurations if any and how they port across app-servers
Thanks
Santosh Maskar

This document is very old.
Take a look at the recent migration guide in the Oracle AS 10.1.3.1 documentation
http://download-uk.oracle.com/docs/cd/B31017_01/migrate.1013/b31269/toc.htm

How to migrate a full J2EE application from WebLogic to NetWeaver?

I have an independent J2EE application which can be run on WebLogic successfully. Now, I want to migrate it to the platform of NetWeaver. Could you tell me how to do with it? And where can I find the jar files of the application I deployed?
Thank you very much!

Have you tried the "exploded" format?
          Also, do you mean Weblogic 6.1 (sp2?).
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          Clustering Weblogic? You're either using Coherence, or you should be!
          Download a Tangosol Coherence eval today at http://www.tangosol.com/
          "adurthy" <[email protected]> wrote in message
          news:[email protected]..
          >
          > HI All,
          >
          > I am trying a migrate a application Jsp application with taglibs from
          tomcat 4.0
          > to weblogic 6.2
          >
          > I tried the example way but none seems to work
          >
          > any help or articles are appreciated
          >
          > thanks
          > sivaji

Error in using the JMS Adater using weblogic queue

I am using weblogic queue in jms adapter to queue the data. i configured the server.xml
     <shared-library name="oracle.weblogic" version="10.1.3">
          <code-source path="D:\product\10.1.3.1\OracleAS_5\jdk\lib\weblogic.jar"/>
     </shared-library>
I got the following error. Any Suggestions?
file:/D:/product/10.1.3.1/OracleAS_5/bpel/domains/default/tmp/.bpel_OSM_OrderRequest_2.0_c68a29fd8af11327e1a8892e8de5a6bb.tmp/Sample.wsdl [ Produce_Message_ptt::Produce_Message(orderRequestMessage) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to:
     Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
     Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
     Loader: oracle.bpel.common:10.1.3
     Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
     Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
The missing class is not available from any code-source or loader in the system.; nested exception is:
     oracle.classloader.util.AnnotatedClassNotFoundException:
     Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
     Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
     Loader: oracle.bpel.common:10.1.3
     Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
     Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
The missing class is not available from any code-source or loader in the system.; nested exception is:
     org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to:
     Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
     Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
     Loader: oracle.bpel.common:10.1.3
     Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
     Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
The missing class is not available from any code-source or loader in the system.; nested exception is:
     oracle.classloader.util.AnnotatedClassNotFoundException:
     Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
     Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
     Loader: oracle.bpel.common:10.1.3
     Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
     Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
The missing class is not available from any code-source or loader in the system.
</summary>
</part>
-<part name="detail">
<detail>
org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to:
     Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
     Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
     Loader: oracle.bpel.common:10.1.3
     Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
     Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
The missing class is not available from any code-source or loader in the system.; nested exception is:
     oracle.classloader.util.AnnotatedClassNotFoundException:
     Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
     Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
     Loader: oracle.bpel.common:10.1.3
     Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
     Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
The missing class is not available from any code-source or loader in the system.

I am able to fix this error by copying "JmsAdapter.jar" to "applib" directory of oc4j_soa.
I was getting a new error.
+"Missing class: oracle.tip.adapter.api.TranslationAware+
+     Dependent class: oracle.tip.adapter.jms.JmsInteractionSpec+
+     Loader: global.libraries:1.0+
+     Code-Source: /D:/SOA1013/j2ee/oc4j_soa/applib/JmsAdapter.jar+
+     Configuration: <code-source> in /D:/SOA1013/j2ee/oc4j_soa/config/server.xml+
+The missing class is available from the following locations:+
+     1. Code-Source: /D:/SOA1013/bpel/lib/orabpel.jar (from <code-source> in /D:/SOA1013/j2ee/oc4j_soa/config/server.xml)+
+     This code-source is available in loader oracle.bpel.common:10.1.3."+
But managed it to fix it by copying "orabpel.jar" to "applib" directory.
We need to restart OC4J once we copy the JAR files.
regards,
S.Vasanth Kumar.

I am getting build error while using weblogic.appc

Hi All,
I am using weblogic 10 server and ejb 3.0 code .
While ejb-complisation i am getting the class not found error.
Please help me in resolving the below issue.
ejb-compile:
[echo] E:\workspace\OMGAdmin\OMGADMIN/omgAdminBuild/omgAdminEAR
[java] Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/descriptor/BeanUpdateListener
[java] at java.lang.ClassLoader.defineClass1(Native Method)
[java] at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
[java] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
[java] at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
[java] at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
[java] at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
[java] at java.security.AccessController.doPrivileged(Native Method)
[java] at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
[java] at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
[java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
[java] at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
[java] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
[java] at java.lang.Class.forName0(Native Method)
[java] at java.lang.Class.forName(Class.java:164)
[java] at weblogic.logging.MessageLogger.<clinit>(MessageLogger.java:46)
[java] at weblogic.logging.WLMessageLogger.log(WLMessageLogger.java:51)
[java] at weblogic.j2ee.J2EELogger.logAppcFailedWithError(J2EELogger.java:5257)
[java] at weblogic.application.compiler.Appc.runBody(Appc.java:179)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:158)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:115)
[java] at weblogic.application.compiler.Appc.main(Appc.java:188)
[java] at weblogic.appc.main(appc.java:14)
[java] Java Result: 1
<target name="ejb-compile" depends="ejb-jar">
     <echo message="${project.EAR.dir}"></echo>
     <java classname="weblogic.appc" fork="yes">
<sysproperty key="weblogic.home" value="${wl.home}"/>
<arg line="-compiler javac ${project.EJB.dir}/omgAdminEJB.jar"/>
<classpath>
<pathelement location="${wl.dir.lib}\weblogic.jar"/>
<pathelement location="${wl.dir.lib}\api.jar"/>
<pathelement location="${wl.dir.lib}\wls-api.jar"/>
          <pathelement location="${project.EAR.dir}\utility.jar"/>
          <pathelement location="${project.lib}\log4j-1.2.13.jar"/>
</classpath>
</java>
     <copy todir="${project.EAR.dir}" >
<fileset dir="${project.EJB.dir}" includes="omgAdminEJB.jar" />
</copy>
     <delete>
<fileset dir="${project.EJB.dir}" includes="omgAdminEJB.jar"/>
</delete>
</target>
above script is my ant task for ejb compilisation
Regd's
Soma.

Finally i am end up with this exception
[java] Exception in thread "main" java.lang.AssertionError: java.lang.reflect.InvocationTargetException
[java] at weblogic.logging.MessageLogger.log(MessageLogger.java:104)
[java] at weblogic.logging.MessageLogger.log(MessageLogger.java:116)
[java] at weblogic.logging.WLMessageLogger.log(WLMessageLogger.java:51)
[java] at weblogic.j2ee.J2EELogger.logAppcFailedWithError(J2EELogger.java:5257)
[java] at weblogic.application.compiler.Appc.runBody(Appc.java:179)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:158)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:115)
[java] at weblogic.application.compiler.Appc.main(Appc.java:188)
[java] at weblogic.appc.main(appc.java:14)
[java] Caused by: java.lang.reflect.InvocationTargetException
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at weblogic.logging.MessageLogger.log(MessageLogger.java:101)
[java] ... 8 more
[java] Caused by: java.lang.NoClassDefFoundError: weblogic/management/DistributedManagementException
[java] at java.lang.Class.getDeclaredMethods0(Native Method)
[java] at java.lang.Class.privateGetDeclaredMethods(Class.java:2365)
[java] at java.lang.Class.privateGetPublicMethods(Class.java:2488)
[java] at java.lang.Class.privateGetPublicMethods(Class.java:2498)
[java] at java.lang.Class.privateGetPublicMethods(Class.java:2498)
[java] at java.lang.Class.privateGetPublicMethods(Class.java:2498)
[java] at java.lang.Class.getMethods(Class.java:1406)
[java] at weblogic.kernel.MBeanStub.initializeFromSystemProperties(MBeanStub.java:51)
[java] at weblogic.kernel.LogMBeanStub.<init>(LogMBeanStub.java:41)
[java] at weblogic.kernel.KernelMBeanStub.<init>(KernelMBeanStub.java:10)
[java] at weblogic.kernel.KernelLogManager$LoggerMaker.<clinit>(KernelLogManager.java:22)
[java] at weblogic.kernel.KernelLogManager.getLogger(KernelLogManager.java:28)
[java] ... 13 more
[java] Java Result: 1
My Build file is
<target name="ejb-compile" depends="ejb-jar">
     <echo message="${project.EAR.dir}"></echo>
     <echo message="${wl.modules.lib}\com.bea.core.descriptor_1.0.1.0.jar" />
     <echo message="${wl.dir.lib}\weblogic.jar" />
     <java classname="weblogic.appc" fork="yes">
<sysproperty key="weblogic.home" value="${wl.home}"/>
<arg line="-compiler javac ${project.EJB.dir}/omgAdminEJB.jar"/>
<classpath>
<pathelement location="${wl.dir.lib}\weblogic.jar"/>
<pathelement location="${wl.dir.lib}\api.jar"/>
<pathelement location="${wl.dir.lib}\wls-api.jar"/>
<pathelement location="${wl.dir.lib}\wlclient.jar"/>
<pathelement location="${wl.modules.lib}\com.bea.core.descriptor_1.0.1.0.jar"/>
          <pathelement location="${project.EAR.dir}\utility.jar"/>
          <pathelement location="${project.lib}\log4j-1.2.13.jar"/>
</classpath>
</java>
     <copy todir="${project.EAR.dir}" >
<fileset dir="${project.EJB.dir}" includes="omgAdminEJB.jar" />
</copy>
     <delete>
<fileset dir="${project.EJB.dir}" includes="omgAdminEJB.jar"/>
</delete>
</target>

Problem using Weblogic 6 and Weblogic 8.1 thin clients from same applicatio

We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
Exceptions:
Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 6.1 SP7?.
     throws following exception while connecting to ?Weblogic 8.1?.
weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
     at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
     at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
     at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
     at weblogic.kernel.Kernel.initialize(Kernel.java:138)
     at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
     at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at java.lang.Class.newInstance0(Class.java:308)
     at java.lang.Class.newInstance(Class.java:261)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
     at javax.naming.InitialContext.init(InitialContext.java:219)
     at javax.naming.InitialContext.<init>(InitialContext.java:195)
     at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
     at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
     at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
java.lang.InternalError: error initializing kernel
     at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
     at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at java.lang.Class.newInstance0(Class.java:308)
     at java.lang.Class.newInstance(Class.java:261)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
     at javax.naming.InitialContext.init(InitialContext.java:219)
     at javax.naming.InitialContext.<init>(InitialContext.java:195)
     at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
     at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
     at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
Case 2: ?Weblogic 8.1? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 8.1?.
     throws following exception while connecting to ?Weblogic 6.1 SP7?.
avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN minor code: 203 completed: No]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more
Couldn't connect to any host
Cause: {1}
javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
Cause: {1}
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more

uday naik <> writes:
The thin-client isn't supported on 6.1, I'm not sure what you are doing.
andy
We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
Exceptions:
Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 6.1 SP7?.
     throws following exception while connecting to ?Weblogic 8.1?.
weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
     at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
     at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
     at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
     at weblogic.kernel.Kernel.initialize(Kernel.java:138)
     at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
     at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at java.lang.Class.newInstance0(Class.java:308)
     at java.lang.Class.newInstance(Class.java:261)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
     at javax.naming.InitialContext.init(InitialContext.java:219)
     at javax.naming.InitialContext.<init>(InitialContext.java:195)
     at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
     at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
     at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
java.lang.InternalError: error initializing kernel
     at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
     at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at java.lang.Class.newInstance0(Class.java:308)
     at java.lang.Class.newInstance(Class.java:261)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
     at javax.naming.InitialContext.init(InitialContext.java:219)
     at javax.naming.InitialContext.<init>(InitialContext.java:195)
     at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
     at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
     at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
Case 2: ?Weblogic 8.1? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 8.1?.
     throws following exception while connecting to ?Weblogic 6.1 SP7?.
avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN minor code: 203 completed: No]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more
Couldn't connect to any host
Cause: {1}
javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
Cause: {1}
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more

Web services with Jdeveloper using weblogic as server

Hi,
I try to test creating PL/SQL web services by using a connection hosted by weblogic server instead of OC4J. The problem is what I try to publish a package of the database in the second stage when it asks for the connection to use, in the list I don't found the connection I create to weblogic . It presents as choice only connections used the server OC4J.
I do not Know if it is possible to publish a package as web service by using weblogic server connection, and how to do it.
can anyone help me please .
Nawal

Web services can only be published to BEA if you install Apache SOAP on BEA and use the Apache SOAP option of JDeveloper. The J2EE Web Services implementation framework is specific to Oracle9iAS.
The PL/SQL Web Services server implementation is based on the J2EE Web Services option and as a result is not really portable to BEA.
To publish a PL/SQL Web service on BEA with JDeveloper you would have to write the Java wrapper code to invoke the stored procedure using standard JDBC and then publish that Java class as a Web service using Apache SOAP. Then if you had Apache SOAP installed on BEA you would be set.
Portability of Web services implementations is a big feature coming with JAX-RPC - currently what most vendors have is interoperability between implementations because of things like SOAPBuilders and WS-I. When JAX-RPC becomes part of J2EE 1.4 roughly in June and vendors start putting out implementations on it you should get closer to portability.
In the meantime, the easiest way to get portability is to use the same SOAP server on both servers - Apache SOAP is a good example.
Hope this helps.
Mike

Problem modifying the connection details in a Report when using Weblogic 12

Hi
I have a j2ee application that uses the Java Reporting Component (JRC). At runtime, the code programmatically changes the connection type and schema name of a crystal report before running it. The connection that was used when designing the report is replaced with new JNDI parameters pointing to a Weblogic/Oracle datasource.
The application works perfectly when using Weblogic 11, but the same code and report fails when deployed to Weblogic 12.
I used Version 12.2.207.916 of the JRC, and updating to the most current version I could find (12.2.217) did not solve the problem.
The code snippet below shows how the connection and schema name is replaced for each of the tables in the report (not all the code is shown here)...
        PropertyBag propertyBag = new PropertyBag();
        propertyBag.put("Database DLL", "crdb_jdbc.dll");
        propertyBag.put("JNDI Datasource Name", jndiName);
        propertyBag.put("Initial Context", "");
            while (tableList.hasNext()) {
                ITable table = tableList.next();
                ITable tableNew = (ITable) table.clone(true);
                IConnectionInfo connectionInfo = table.getConnectionInfo();
                connectionInfo.setAttributes(propertyBag);
                connectionInfo.setKind(ConnectionInfoKind.SQL);
                tableNew.setQualifiedName(newQualifier + "." + table.getName());
                tableNew.setConnectionInfo(connectionInfo);
                dbController.setTableLocation(table, tableNew);
The setTableLocation() function throws the following exception ...
2014-05-13 16:46:27,173 ERROR [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] JRCCommunicationAdapter         detected an exception: Unexpected database connector error
                at com.crystaldecisions.reports.queryengine.Table.u7(SourceFile:2409)
                at com.crystaldecisions.reports.dataengine.datafoundation.AddDatabaseTableCommand.new(SourceFile:529)
                at com.crystaldecisions.reports.common.CommandManager.a(SourceFile:71)
                at com.crystaldecisions.reports.common.Document.a(SourceFile:203)
                at com.businessobjects.reports.sdk.requesthandler.f.a(SourceFile:175)
                at com.businessobjects.reports.sdk.requesthandler.DatabaseRequestHandler.byte(SourceFile:1079)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter.do(SourceFile:1167)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter.if(SourceFile:661)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter.a(SourceFile:167)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.a(SourceFile:529)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.call(SourceFile:527)
                at com.crystaldecisions.reports.common.ThreadGuard.syncExecute(SourceFile:102)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter.for(SourceFile:525)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter.int(SourceFile:424)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(SourceFile:352)
                at com.businessobjects.sdk.erom.jrc.a.a(SourceFile:54)
                at com.businessobjects.sdk.erom.jrc.a.execute(SourceFile:67)
                at com.crystaldecisions.proxy.remoteagent.RemoteAgent$a.execute(SourceFile:716)
                at com.crystaldecisions.proxy.remoteagent.CommunicationChannel.a(SourceFile:125)
                at com.crystaldecisions.proxy.remoteagent.RemoteAgent.a(SourceFile:537)
                at com.crystaldecisions.sdk.occa.report.application.ds.a(SourceFile:186)
                at com.crystaldecisions.sdk.occa.report.application.an.a(SourceFile:108)
                at com.crystaldecisions.sdk.occa.report.application.b0.if(SourceFile:148)
                at com.crystaldecisions.sdk.occa.report.application.b0.b(SourceFile:95)
                at com.crystaldecisions.sdk.occa.report.application.bb.int(SourceFile:96)
                at com.crystaldecisions.proxy.remoteagent.UndoUnitBase.performDo(SourceFile:151)
                at com.crystaldecisions.proxy.remoteagent.UndoUnitBase.a(SourceFile:106)
                at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(SourceFile:2159)
                at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(SourceFile:543)
                at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(SourceFile:3898)
                at com.crystaldecisions.sdk.occa.report.application.DatabaseController.setTableLocation(SourceFile:2906)
                at com.systest.reporting.engine.crystal.CrystalReportEngine.replaceConnection(CrystalReportEngine.java:523)
                at com.systest.reporting.engine.crystal.CrystalReportEngine.changeDataSource(CrystalReportEngine.java:449)
                at com.systest.CrystalReportPane.setReportDataSourceDetails(CrystalReportPane.java:170)
                at com.systest.CrystalReportPane.commandLoad(CrystalReportPane.java:136)
                at com.systest.ReportRunner.CrystalReport.Load(CrystalReport.java:401)
                at com.systest.ReportRunner.SaveReportToFile(ReportRunner.java:1385)
Any idea what I can do to fix this ?
Thanks in advance!

Last reference in any documentation re. version of supported weblogic is 10.3.x. And it may very well be that things worked in weblogic 11, but as versions go by the differences get bigger and eventually the app stops working.
I'll ping the Program Manager for definitive info and future support. Once I have the info, I'll update this Discussion.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter

Call weblogic EJB without using weblogic.jndi.T3InitialContextFactory

I am trying to call an ejb on a weblogic server without using weblogic.jndi.T3InitialContextFactory.
The context retrieval is as follows:
Properties table = new Properties();
table.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
table.put(Context.PROVIDER_URL, "iiop://localhost:7001");
Context context = new InitialContext(table);
return context;
but when I run the client I am getting the follwing error:
javax.naming.CommunicationException: Cannot connect to ORB [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No]
at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:362)
at com.sun.jndi.cosnaming.CNCtx.initUsingIiopUrl(CNCtx.java:289)
at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:245)
at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:209)
at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:69)
at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:32)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.test.TestDirectDocumentLoad.getContext(TestDirectDocumentLoad.java:59)
at com.test.TestDirectDocumentLoad.loadDocs(TestDirectDocumentLoad.java:139)
at com.test.TestDirectDocumentLoad.main(TestDirectDocumentLoad.java:116)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.se.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:173)
at com.sun.corba.se.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:65)
at com.sun.corba.se.internal.iiop.GIOPImpl.getConnection(GIOPImpl.java:67)
at com.sun.corba.se.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:652)
at com.sun.corba.se.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:594)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1105)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:340)
... 12 more
I have the J2EE jar on the client path and all....but can't get through this error
need help guys!
Samir

Samir j <> writes:
Make sure IIOP is enabled on the server side. There was a bug in
earlier 8.1 config wizards that defaulted it to off.
andy
I am trying to call an ejb on a weblogic server without using weblogic.jndi.T3InitialContextFactory.
The context retrieval is as follows:
Properties table = new Properties();
table.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
table.put(Context.PROVIDER_URL, "iiop://localhost:7001");
Context context = new InitialContext(table);
return context;
but when I run the client I am getting the follwing error:
javax.naming.CommunicationException: Cannot connect to ORB [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No]
at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:362)
at com.sun.jndi.cosnaming.CNCtx.initUsingIiopUrl(CNCtx.java:289)
at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:245)
at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:209)
at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:69)
at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:32)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.test.TestDirectDocumentLoad.getContext(TestDirectDocumentLoad.java:59)
at com.test.TestDirectDocumentLoad.loadDocs(TestDirectDocumentLoad.java:139)
at com.test.TestDirectDocumentLoad.main(TestDirectDocumentLoad.java:116)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.se.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:173)
at com.sun.corba.se.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:65)
at com.sun.corba.se.internal.iiop.GIOPImpl.getConnection(GIOPImpl.java:67)
at com.sun.corba.se.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:652)
at com.sun.corba.se.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:594)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1105)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:340)
... 12 more
I have the J2EE jar on the client path and all....but can't get through this error
need help guys!
Samir

When to use the -clusterable extra rmic option?

          Hi,
          We are trying to do a clustered deployment on the WLS 701. I am trying to figure
          out all the things that need to be on for clustering to work successfully. Currently
          I am focused on the EJBs. Here is what I have found:
          o For remote SLSBs there is no need to specify home-is-clusterable in weblogic-ejb-jar.xml
          because the default value is true?
          o For remote SLSBs there is no need to specify is-clusterable in weblogic-ejb-jar.xml
          because the default value is true?
          o For Entity Beans is-clusterable doesn't make sense?
          o For local Entity Benas home-is-clusterable doesn't make sense?
          o Are the options for home-is-clusterable and is-cluterable enough or do we have
          to specify -clusterable as extra rmic option under ejbc options?
          Thank you so much,
          -Bart Simpson


Hi,
          How are you doing? Is anybody out there using the -clusterable
          option? Why?
          Does the option make sense even if the both the JSP/Servlets and EJBs
          are deployment on the name node?
          Thank you so much,
          -Bart Simpson
          "Bart Simpson" <[email protected]> wrote in message news:<[email protected]>...
          > Hi,
          >
          > We are trying to do a clustered deployment on the WLS 701. I am trying to figure
          > out all the things that need to be on for clustering to work successfully. Currently
          > I am focused on the EJBs. Here is what I have found:
          >
          > o For remote SLSBs there is no need to specify home-is-clusterable in weblogic-ejb-jar.xml
          > because the default value is true?
          > o For remote SLSBs there is no need to specify is-clusterable in weblogic-ejb-jar.xml
          > because the default value is true?
          > o For Entity Beans is-clusterable doesn't make sense?
          > o For local Entity Benas home-is-clusterable doesn't make sense?
          > o Are the options for home-is-clusterable and is-cluterable enough or do we have
          > to specify -clusterable as extra rmic option under ejbc options?
          >
          > Thank you so much,
          > -Bart Simpson

ANN: J2EE Applications & BEA WebLogic Hardcopies Available!

** J2EE Applications & BEA WebLogic Hardcopies Available! **
The first hardcopies of the only programming book to cover J2EE & WebLogic 6
are now available. For those of you that have already ordered, we thank you.
In just a few short weeks we have moved up to the No. 42 spot on Amazon.
If you have not ordered already, you can order now and copies will be
shipped in just a few short days. The book can be located Amazon.com at the
following URL:
http://www.amazon.com/exec/obidos/ASIN/0130911119/ref=ase_learnweblogic/103-
5396741-5920623
More information on this book can be located at:
http://www.learnweblogic.com/.
** Overview **
Building J2EE Applications & BEA WebLogic is targeted at Java programmers
developing applications for the BEA WebLogic platform, the leading Web
Application Server in the marketplace today. This book focuses on best
practices for developing enterprise applications using the WebLogic APIs.
After reading this book, intermediate or professional-level Java developers
will possess the skills and knowledge required to develop scalable and
robust applications on the WebLogic platform.
The book combines reference and tutorial, taking a step-by-step approach
that introduces each API and uses it to build a component of the WebAuction
application, which supports on-line Auctioning on the Web. All software
needed to build the sample application is included on a CD-ROM that
accompanies the book. The WebAuction project gives users the opportunity to
explore significant areas of building a distributed Enterprise Java
application, including:
· Planning in advance for scalability and deployment
· Building presentation logic
· Establishing database connectivity
· Creating Enterprise Java Beans for the BEA WebLogic application server
· Packaging the whole application so that it can be easily managed and
maintained.
** About the Authors **
Rob Woollen is a Senior Software Engineer at BEA Systems. He is currently
the lead developer for the WebLogic Server EJB Container. Before joining
BEA, Rob worked on UNIX Kernel networking for Hewlett-Packard. Rob holds a
Bachelors degree in Computer Science from Princeton University.
Michael Girdley is the Director of Product Management for WebLogic Server at
BEA, a role in which he acts as chief marketing liaison to over 200
engineers. An experienced application developer in Java, HTML, C, and C++,
Michael is a co-author of Web Programming with Java (Sams-net Publishing,
1996) and Java Unleashed, Second Edition (Sams-net Publishing, 1997).
Michael holds a Bachelors degree in Computer Science with Honors from
Lafayette College.
Sandra L. Emerson is a technical writer and consultant with 20 years'
experience in the software industry. She is a co-author of four computer
trade books: The Business Guide to the UNIX System (Addison-Wesley, 1984);
Database for the IBM PC (Addison-Wesley, 1984); Troff Typesetting for UNIX
Systems (Prentice-Hall, 1987); and The Practical SQL Handbook
(Addison-Wesley, 1989-99). The fourth edition of The Practical SQL Handbook
is scheduled for Fall, 2000.

** J2EE Applications & BEA WebLogic Hardcopies Available! **
The first hardcopies of the only programming book to cover J2EE & WebLogic 6
are now available. For those of you that have already ordered, we thank you.
In just a few short weeks we have moved up to the No. 42 spot on Amazon.
If you have not ordered already, you can order now and copies will be
shipped in just a few short days. The book can be located Amazon.com at the
following URL:
http://www.amazon.com/exec/obidos/ASIN/0130911119/ref=ase_learnweblogic/103-
5396741-5920623
More information on this book can be located at:
http://www.learnweblogic.com/.
** Overview **
Building J2EE Applications & BEA WebLogic is targeted at Java programmers
developing applications for the BEA WebLogic platform, the leading Web
Application Server in the marketplace today. This book focuses on best
practices for developing enterprise applications using the WebLogic APIs.
After reading this book, intermediate or professional-level Java developers
will possess the skills and knowledge required to develop scalable and
robust applications on the WebLogic platform.
The book combines reference and tutorial, taking a step-by-step approach
that introduces each API and uses it to build a component of the WebAuction
application, which supports on-line Auctioning on the Web. All software
needed to build the sample application is included on a CD-ROM that
accompanies the book. The WebAuction project gives users the opportunity to
explore significant areas of building a distributed Enterprise Java
application, including:
· Planning in advance for scalability and deployment
· Building presentation logic
· Establishing database connectivity
· Creating Enterprise Java Beans for the BEA WebLogic application server
· Packaging the whole application so that it can be easily managed and
maintained.
** About the Authors **
Rob Woollen is a Senior Software Engineer at BEA Systems. He is currently
the lead developer for the WebLogic Server EJB Container. Before joining
BEA, Rob worked on UNIX Kernel networking for Hewlett-Packard. Rob holds a
Bachelors degree in Computer Science from Princeton University.
Michael Girdley is the Director of Product Management for WebLogic Server at
BEA, a role in which he acts as chief marketing liaison to over 200
engineers. An experienced application developer in Java, HTML, C, and C++,
Michael is a co-author of Web Programming with Java (Sams-net Publishing,
1996) and Java Unleashed, Second Edition (Sams-net Publishing, 1997).
Michael holds a Bachelors degree in Computer Science with Honors from
Lafayette College.
Sandra L. Emerson is a technical writer and consultant with 20 years'
experience in the software industry. She is a co-author of four computer
trade books: The Business Guide to the UNIX System (Addison-Wesley, 1984);
Database for the IBM PC (Addison-Wesley, 1984); Troff Typesetting for UNIX
Systems (Prentice-Hall, 1987); and The Practical SQL Handbook
(Addison-Wesley, 1989-99). The fourth edition of The Practical SQL Handbook
is scheduled for Fall, 2000.

Using weblogic clustering to improve permance in J2EE applications

Similar Messages

Maybe you are looking for