Distributing a Java EE Application Client (Thin Client)

Hi,
I'm following the instructions in Section 4 Developing a Java EE Application Client (Thin Client) in Oracle® Fusion Middleware Programming Stand-alone Clients for Oracle WebLogic Server, 11g Release 1 (10.3.1), Part Number E13717-01.
I packaged the application client in an ear. If I set up my environment using C:\bea10\wlserver_10.3\server\bin\setWLSEnv.cmd. I can extract the application client using a command line like:
java weblogic.ClientDeployer myear.ear myclient
I can execute the client using a command line like:
java weblogic.j2eeclient.Main myclient.jar t3://localhost:7003
However, I would like to run the application client on a client machine (i.e., a machine without WebLogic installed). I thought I could use one of the wl*client.jar files such wlclient.jar, wlfullclient.jar, etc. I started with wlfullclient.jar.
If I try to extract the application client with a command line like
java -classpath wlfullclient.jar weblogic.ClientDeployer myear.ear myclient
I get the following error:
Exception in thread "main" java.lang.NoClassDefFoundError: com/bea/xml/XmlException
at weblogic.descriptor.BasicDescriptorManager.getMarshallerFactory(BasicDescriptorManager.java:143)
at weblogic.descriptor.BasicDescriptorManager.getDescriptorFactory(BasicDescriptorManager.java:183)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:320)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:301)
at weblogic.ClientDeployer.findAltDDUri(ClientDeployer.java:210)
at weblogic.ClientDeployer.processClientJar(ClientDeployer.java:107)
at weblogic.ClientDeployer.processClientJar(ClientDeployer.java:75)
at weblogic.ClientDeployer.main(ClientDeployer.java:43)
Caused by: java.lang.ClassNotFoundException: com.bea.xml.XmlException
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
... 12 more
Next I tried using the jar previously extracted on the server and tried to run it using:
java -classpath wlfullclient.jar weblogic.j2eeclient.Main myclient.jar t3://localhost:7003
I get the following error:
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/j2ee/descriptor/wl/WeblogicApplicationClientBean
at weblogic.j2eeclient.Main.fillEnvironment(Main.java:326)
at weblogic.j2eeclient.Main.run(Main.java:185)
at weblogic.j2eeclient.Main.main(Main.java:924)
Caused by: java.lang.ClassNotFoundException: weblogic.j2ee.descriptor.wl.WeblogicApplicationClientBean
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
... 3 more
Is it possible to extract and execute an application client on a machine without WebLogic server? If so, what jars do I need? If not, why not?
I'm testing using WebLogic 10.3.1 on a Windows XP SP2 machine using JDK 1.6.0_05.
Thanks in advance,
Keith

Hello,
I tried doing pre-compilation of jsps using the weblogic.appc and getting the below exception.
Can any one advise the jar file containing the below class file so that I can add in the classpath and try for it.
java.lang.ClassNotFoundException: com.bea.xml.XmlException
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at weblogic.descriptor.BasicDescriptorManager.getMarshallerFactory(BasicDescriptorManager.java:137)
at weblogic.descriptor.BasicDescriptorManager.getDescriptorFactory(BasicDescriptorManager.java:171)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:303)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoa
r2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.ja
:409)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorL
der2.java:759)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java
68)
at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:311)
at weblogic.application.compiler.CompilerCtx.setApplicationDescriptor(CompilerCtx.java:138)
at weblogic.application.compiler.AppcUtils.setDDs(AppcUtils.java:142)
at weblogic.application.compiler.flow.DescriptorParsingFlow.compile(DescriptorParsingFlow.java:57)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
at weblogic.application.compiler.EARCompiler.compile(EARCompiler.java:49)
at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:118)
at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:43)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
at weblogic.application.compiler.Appc.runBody(Appc.java:181)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.Appc.main(Appc.java:192)
at weblogic.appc.main(appc.java:14)
com.bea.xml.XmlException

Similar Messages

  • Is EJB Java's solution for Thin Clients??

    I want to create an API that controls my odbc layer and place it on my server, not the clients.
    What is the best java solution to create thin client java applications?

    Well that's a big question but I'll give it a go. Use J2EE and let your clients be web browsers. Do all your work on the application server with servlets, JSPs and EJBs. That's about as thin as you can get. Browsers don't give you the best interface in the world but you gain:
    1> No 10meg JRE installation on each client machine.
    2> No worrying about the JRE version.
    3> All upgrades occur near you so no client version to worry about when you make changes.
    blah blah blah

  • Issue with non-english application in thin client - virtual directory issue

    Hi,
    I have just completed Siebel 8 installation on solaris machine along with SunOne Web server 6.1.
    I have installed both ENU and ARA language packs for Siebe Enterprise, Sweapps.
    The issue is after installation and repository installation for both ENU and ARA, I am able to open only ENU applications in thin client.
    When I try to open the ARa applications the browser gives "Page not found" error.
    I have verified first, whether the Siebel components running or not. Confirmed that for example for Callcenter SCCObjMgr_ara component is active and online.
    But what I observed is, in SUNOne web server instance's config folder, there is a file obj.conf.
    In this file there are entries for only enu applications like,
    NameTrans fn="pfx2dir" from="/callcenter_enu" dir="/siebelapp/sweapp/public/enu"
    There are no links for ARA applications.
    I think this could be the reason for issue.
    But while installing and configuring sweapps, I have selected the logical profile location as "/siebelapp/gtwysrvr/admin/Webserver".
    So this should create such links in obj.conf for ARA as it created for ENU apps. But it didn't happend.
    Please advise, how to get the ARA applications.
    Thanks
    Vamshi
    Edited by: user4619223 on Mar 23, 2010 11:36 AM

    I see some message about a proxy. Have you checked that you can use the proxy from you network?
    If not you should turn the proxy off.
    Timo

  • Calling report from forms while running the application from thin clients

    I am using thin client technology with 64MB RAM for running developer 6i application.
    The server has windows 2000 advanced server with 256 MB RAM.
    When I run the apllication from a single client, it works fine even for multiple windows.
    But the moment I switch on more thin clients, the client which fired the printing job first works fine, while the others allow data entry using forms but any call to report for direct printing throws an illegal condition error. I have tried both run_product and host option for running reports. The error returned is the same.
    Howver if the report is run from command prompt simultaneously from both the clients it works fine.
    Immediate help required in this case
    chandandeep

    Hi,
    you better off using Run_Report_Object() instead of Run_Product(). There is a Whitepaper available on otn.oracle.com/products/forms that details this. The problem that you run into is that Forms Services(thin clients) are multi user environments while Reports called via Run_Product() is a single user environment. This means that the Reports Runtime does not handle Reports requests in parallel but sequential one at a time. The first user blocks the runtime engines and all other hang for this time.
    Fran

  • THICK CLIENTS & THIN CLIENTS

    Can any body please tell me in detail what is the difference between a Thick client and a Thin client. Also tell me using either of these in specific occassions.

    And it's normally called a 'Rich Client' not 'Thick Client'.No, "rich client" is a newer developer.
    s/developer/development/I think it's more than a when Sales/Marketing people wanted to promote thin client solutions (during the fashionable thin 90's) they used devisive language of (Thick/Fat) against the alternative traditional Client Server solutions even though these could be Rich or Thin. I remember when Applets where considered thin, then it had to be Web-Pages to be really Thin and now that things have gone full circle with the introduction of things like AJAX and WebStart they use the old^Wnew terminology, or Rich Clients to distance it from the negitive associations of Thick and Fat.
    To me, fashions come and go but they will always be Thin or Rich :)

  • Need java plugin for thin client like HP compaq t 5000

    Hello everybody,
    I need to know if there any java plugin for Internet Explorer on windows CE.net on a thin clinet like HP compaq t5000, my problem is that i have an oracle form that access to oracle databse, on the client i have thin client HP compaq t5000, oracle support told me to post my problem in java forums since there's no jinitiator support for windows ce.net, as the oracle forms is based on java applet, so it could be a solution if i can find a java plugin for windows ce.net on my thin client like that i can see the oracle form.........................
    please can anyone help me with a link where i can download a java plugin for windows ce.net and how to install it on such operating system...................
    Thank you in advance

    hello again, thank you for ur response, but please can u help me with how i can install the Creme jvm that support applets on the hp compaq t5000 under windows ce.net, because actually i don't have any idea on how we install software on such machine, coz it seems the isntallation on them it different than the normal windows xp...... i download the demo creme jvm zip file and i 'm not able to install it, if it is possible can u provide me with step by step instruction, just need to test my application on the demo version first, thank u in advance.....

  • How i upload a web page named index.html generated by NI Web UI Builder in thin client application on world wide Web

    Hello All,
                   I have an example which use simulated signal with its web service generated by LabVIEW. Then an application of this web service was created using NI web UI builder. And application was build and deployed on NI Cloud Portal, a zip file was downloaded of that project  after build and deploying application.
    The downloaded file contain a thin client application like :index.html page, readme file etc.
                  Now problems is this index.html runs easily on http://localhost:8080/appname/index.html or on my computer name like
    http://iaa42:8080/appname/index.html web page runs and shows updated values in indicators and graphs  but when i use ip address of my system like http://192.168.1.6:8080/appname/index.html , index.html runs but the values in indicator and graphs remains 0 (zero) constantly.     how can i get all indicators and graphs updating continously on by using my ip address like same when i use localhost or computer name in url bar.    1st problem is this.
    Now 2nd question.
                 I get a page index.html in a zip file built by NI web UI builder now i want this page to be viewed by every one world wide
    where should i upload that code. Should NI Cloud Portal be my hosting server for that web page ? or i have to purchase a domain other than NI cloud portal?
     Thanks in Advance
    Regards
    Waqas

    Hi Waqas,
    For your first question, my first thoughts turn to your router (which I assume you are using with a 192.168.x.x address). Are you sure you are configuring your ports and firewalls to allow NI services to function? Here is a really good resource on how to check if your ports and firewalls are configured properly:
    http://www.ni.com/white-paper/12402/en/
    For your second question, when you deploy a web service you are hosting it on your local machine. If you wanted to host it elsewhere (i.e. another server or another domain) you would have to be sure that the server hosting your application has the LabVIEW run-time engine installed. 
    Rick C.

  • Reports 9i/10g J2EE Thin Client for Websphere Application Server 5.x /6.x

    We are having Reports developed in 6i which needs to be migrated to Reports 9i/10G and we want to deploy these reports in web using Websphere Application Server 5.x /6.x without Oracle iAS.
    Do we have Reports 9i/10g J2EE Thin Client for Websphere Application Server 5.x /6.x and if so please let me know.
    Also if anybody has the configuration details please let me know?
    Thanks in Advance.

    No there is not. I don't think you can use reports services with Websphere - besides as far as I know it is not supported by Oracle (not anywhere in their support matrix).

  • How to launch a Java WebStart application with older JREs when Java 7u25 is on the client?

    How can I launch older versions of my Java WebStart application, that are built and run with Java 7u21 or earlier, even if Java 7u25 is installed locally on the client? Application launch and behaviour must be reliable and consistent.
    Background:
    As of 7u25 (and later), Java Webstart applications launch with a different class loader than pre-7u25.
    My Java Webstart application has supported versions that were built with older versions of the JDK (e.g. Java 5, 6, 7u21 or earlier). These applications run with their required JRE version, enforced through JNLP. Once Java 7u25 is installed locally, these older applications fail to launch, due to classloader differences.
    The question is: what is required to run older Java WebStart applications even if 7u25 (or later) Java Webstart is installed locally on the client?

    I confirm your findings when using shortcuts to try specific versions of JavaWS with 7u25 or later installed:
    JRE 5u14 launched and the classloader was as pre 7u25
    JRE 6u43 would not launch
    JRE 7u21 launched but the classloader was not as pre 7u25
    You can launch the shortcut with the JavaWS -verbose option to display a messagebox with valuable information.
    I am keeping a close watch on this thread.

  • Thin clients, labs, and applications

    We have thin clients in some labs and have a specific virtual desktop load specific for that lab.  The issue;  students do NOT have to log into the network and we want to change this.
    Our issue:
    We have 10 licenses for an application in a lab.  The virtual desktop has this application for 10 computers within the specific lab.
    If we have students log onto the network, they will have to option of selecting which virtual desktop to open (multiple courses taken by the student, multiple labs = multiple virtual desktops)
    If a student logs in from the library, they will see all the virtual desktops as well and could use one of the 10 mentioned above, thus using up one of the virtual desktop application licenses.
    This leaves one student in the lab not able to connect.
    Question:
    Is there a way to either limit what the student can select based on location/IP address or is there another way to make sure that virtual desktop is only used within that lab?
    I have been told that virtual desktops are user based and therefore cannot be altered in this way...so, checking here.
    TIA,
    --cdburns

    We have a similar requirement, as we are replacing physical labs with VDI zero and thin clients and want them to behave similarly.  Our physical lab environment had different software setups for different locations (Geology, Audiology, Nursing, etc.).  We have locked down access to the VDI environment (the broker) from on-campus only, and the majority of our zero and thin clients are setup to auto-login to a specific pool - getting rid of the areas where students can select which pool to log into.
    There is one exception where we had to be more harsh because of compliance reasons.  We could only let students log into a specific lab pool if they were using specific thin/zero clients.  You've already mentioned our solution to this as we used VLANs to restrict this access.  The VMs in the pool resides in a VLAN that only allows the PCoIP protocol access from another VLAN where the authorized zero/thin clients reside.  While authorized students would be able to see the pool selection if presented on their own or unrestricted device - they wouldn't be able to fully take control as the PCoIP connection wouldn't work.
    Another option is to use the broker labels.  We abandoned this option as it didn't seem to be scalable and we'd have to potentially setup multiple broker servers in order to accomplish this.
    I'm waiting for vmware to come out with a better solution.  You'd expect there to be a desire to restrict access to various pools based on the client endpoint or location.

  • Adobe Air Vs Thin Client Application

    Hi,
    I have very little knowledge of Adobe Air. I would like to
    know the basic difference between Adobe Air & thin client
    applications.
    Also, does Adobe air supports web applications? if yes then
    how it interacts with centralize database which resides on main
    server?
    Does Adobe Air works only with MySQL?
    Can anyone help on this?
    Thanks in advance!!

    quote:
    Originally posted by:
    ChinmayeePune
    I would like to know the basic difference between Adobe Air
    & thin client applications.
    I don't see that there necessarily is a
    difference. You can use AIR to build a thin client. You can use AIR
    to build a thick client. It's a tool. It doesn't tell you what to
    build.
    quote:
    Also, does Adobe air supports web applications?
    AIR includes several networking facilities which
    can be used to interact with a web server.
    quote:
    how it interacts with centralize database which resides on
    main server?
    It can do it the same way a browser does: by
    sending requests over HTTP, handled by server side code that
    manipulates the DB. If you have a "Web Service" API, AIR supports
    all the SOAP ****, too. And, there is a raw network API if you have
    to hand-roll your low-level protocol.
    quote:
    Does Adobe Air works only with MySQL?
    AIR doesn't support MySQL at all. The only
    native DB support it has is for SQLite, which is used for databases
    on the local file system where the AIR app resides. To access a
    remote DB, you have to use some form of custom networking to reach
    it.
    Theoretically, you could write a MySQL network client using
    the raw client socket functionality, but I don't believe this
    protocol is documented. You could extract it from the MySQL source
    code, but...eck. Better to set up some kind of web service
    API.

  • JMS thin client application

              I am developing a JMS thin client application hosted on a seperate UNIX box than
              the JMS server which is provided by a third party.
              Are wljmsclient.jar and wlclient.jar files from BEA Weblogic workshop 8.1 the
              only JMS API
              that I need for my JMS thin client application?
              Is there any licensing fees for using these two jar files to build JMS thin client
              applications?
              Thanks
              

              Yazid Benkhellat wrote:
              > I am developing a JMS thin client application hosted on a seperate UNIX box than
              > the JMS server which is provided by a third party.
              > Are wljmsclient.jar and wlclient.jar files from BEA Weblogic workshop 8.1 the
              > only JMS API
              > that I need for my JMS thin client application?
              Yes, unless you are using WorkShop WebService APIs. I'm not
              sure if you need more (post to work-shop newsgroups to find out).
              > Is there any licensing fees for using these two jar files to build JMS thin client
              > applications?
              No!
              > Thanks
              >
              Tom, BEA
              

  • Java Thin Client Questions

    If you want to do Listener Load Balancing and you are using a Java Thin client the URL needs to only contain the SERVICE_NAME and not the INSTANCE_NAME. Are you suppose to specify all of the addresses or are you just suppose to pick one?
    ie
    jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=node2)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=eric)(SERVER=DEDICATED)))

    Hi,
    You will have to add all the addresses. Look at the following extract:
    jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=ON)(ADDRESS=(PROTOCOL=TCP)(HOST=node1-vip)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=node2-vip)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=eric)(SERVER=DEDICATED)))
    When users connect to the database using the eric as shown above, they are actually connecting to database using the Oracle 10g Service named eric. Users need not to know which cluster node or database instance is serving the eric service. You shoudl always use node1-vip and node2-vip in the address list not the physical hostname/IP. In case node1 goes down user can still connect to the database if service eric is configured to run on both nodes.
    Just setting the LOAD_BALANCE=ON will not balance the load if the service being used is not configured to run on cluster nodes listed in the tns alias's address list.
    Any correction is welcome...
    -Harish Kumar Kalra

  • Database connection encryption and integrity with ColdFusion and Oracle thin client

    As ColdFusion datasource we are using the Oracle thin client to  connect with the database. So, basically we are using a JDBC URL such as  jdbc:oracle:thin:@... and as Driver Class oracle.jdbc.OracleDriver. This works successfully however we would like to set encryption and  integrity parameters as well. In Java this is done similarly by setting a  Properties object prior to getting a connection as follows:
    Properties prop = new Properties();
    prop.put("oracle.net.encryption_client", "REQUIRED");
    prop.put("oracle.net.encryption_types_client", "( DES40 )");
    prop.put("oracle.net.crypto_checksum_client", "REQUESTED");
    prop.put("oracle.net.crypto_checksum_types_client", "( MD5 )");
    OracleDataSource ods = new OracleDataSource();
    ods.setProperties(prop);
    ods.setURL("jdbc:oracle:thin:@localhost:1521:main");
    Connection conn = ods.getConnection();
    Is there a way that I can pass these parameters to the ColdFusion  datasource. Ideally, I would love to do this centrally in such way that a  change to all the cfquery or cfstoredproc is not needed.
    I also know that in application servers such as Oracle AS there is an  option when creating a datasource which says "Add Properties". In there  you can add such properties. So, I was thinking of maybe creating a  JNDI DS in the app. server and then magically connecting to it but this  may have some impacts on the app.
    Besides this I was also thinking of communicating with the CF  datasource through the CF admin API (cfide.adminapi.administrator) and  also the option of extending the Oracle driver so that when CF connects  with it these params are already set.
    I would love to have your professional opinion and suggestions on this.

    I believe the thin driver actually needs the IP address (not the DNS name). Also, is "java" the name of the Oracle instance to which you are trying to connect?
    Try the following:String driver = "jdbc:oracle:thin";
    String dbIP = "W2RZ1NXG01's IP address";
    String dbPort = "1530";
    String dbSid = "java";
    String dbUser = "Admin";
    String dbPswd = "apassword";
    String cnctStr = driver + ":@" + dbIP + ":" + port + ":" + dbSid;
    try
        Class.forName("oracle.jdbc.driver.OracleDriver");
        con = DriverManager.getConnection( cnctStr, dbUser, dbPswd );
        stmt = con.createStatement();
        stmt.executeUpdate(createString);
        stmt.close();
        con.close();
    catch(SQLException ex)
        System.err.println( "The following SQLException occurred: " + ex );
        System.err.println( "Message: " + ex.getMessage() );

  • 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

Maybe you are looking for