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

Similar Messages

  • ModuleException in running web app in Myeclipse on weblogic server

    Hi,
    I got following error while runing my web app in myeclipse using weblogic 9.2
    <Jul 22, 2010 10:11:48 AM IST> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    C:\Local\weblogic92\weblogic92\platform\lib\p13n\p13n-schemas.jar;C:\Local\weblogic92\weblogic92\platform\lib\p13n\p13n_common.jar;C:\Local\weblogic92\weblogic92\platform\lib\p13n\p13n_system.jar;C:\Local\weblogic92\weblogic92\platform\lib\wlp\netuix_common.jar;C:\Local\weblogic92\weblogic92\platform\lib\wlp\netuix_schemas.jar;C:\Local\weblogic92\weblogic92\platform\lib\wlp\netuix_system.jar;C:\Local\weblogic92\weblogic92\platform\lib\wlp\wsrp-common.jar>
    <Jul 22, 2010 10:11:49 AM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.5.0_10-b03 from Sun Microsystems Inc.>
    <Jul 22, 2010 10:11:50 AM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 MP2 Mon Jun 25 01:32:01 EDT 2007 952826 >
    <Jul 22, 2010 10:11:53 AM IST> <Info> <WebLogicServer> <BEA-000215> <Loaded License : C:\Local\weblogic92\license.bea>
    <Jul 22, 2010 10:11:53 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jul 22, 2010 10:11:53 AM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Jul 22, 2010 10:11:54 AM IST> <Notice> <Log Management> <BEA-170019> <The server log file C:\Local\weblogic92\user_projects\domains\base_domain2\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
    <Jul 22, 2010 10:11:56 AM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jul 22, 2010 10:12:10 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Jul 22, 2010 10:12:10 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    *<Jul 22, 2010 10:12:19 AM IST> <Error> <HTTP> <BEA-101216> <Servlet: "action" failed to preload on startup in Web application: "web1".*
    java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
    *     at org.apache.struts.action.ActionServlet.<clinit>(ActionServlet.java:226)*
    *     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:494)*
    *     Truncated. see log file for complete stacktrace*
    *>*
    *<Jul 22, 2010 10:12:22 AM IST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application '_appsdir_CostBasisReport_dir'.*
    *weblogic.application.ModuleException: [HTTP:101216]Servlet: "action" failed to preload on startup in Web application: "web1".*
    java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
    *     at org.apache.struts.action.ActionServlet.<clinit>(ActionServlet.java:226)*
    *     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:494)*
    *     at java.lang.Class.newInstance0(Class.java:350)*
    *     at java.lang.Class.newInstance(Class.java:303)*
    *     at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:252)*
    *     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)*
    *     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)*
    *     at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)*
    *     at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)*
    *     at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)*
    *     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:507)*
    *     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1715)*
    *     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1692)*
    *     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1612)*
    *     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2750)*
    *     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)*
    *     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)*
    *     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)*
    *     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)*
    *     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)*
    *     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)*
    *     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)*
    *     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)*
    *     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)*
    *     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)*
    *     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)*
    *     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)*
    *     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)*
    *     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)*
    *     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)*
    *     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)*
    *     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:181)*
    *     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:358)*
    *     at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)*
    *     at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:186)*
    *     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)*
    *     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)*
    *     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)*
    *     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)*
    *     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)*
    *     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)*
    *     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
    *     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
    *     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)*
    *     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:891)*
    *     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)*
    *     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)*
    *     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)*
    *     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)*
    *     Truncated. see log file for complete stacktrace*
    java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
    *     at org.apache.struts.action.ActionServlet.<clinit>(ActionServlet.java:226)*
    *     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:494)*
    *     Truncated. see log file for complete stacktrace*
    *>* <Jul 22, 2010 10:12:24 AM IST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "base_domain2" running in Development Mode>
    <Jul 22, 2010 10:12:24 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Jul 22, 2010 10:12:24 AM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

    Hi,
    U will need to add two Jar files inside the "<DOMAIN_HOME>\lib" directory:
    1). commons-logging-1.0.1.jar (This Jar is available with WLS Installation...)
    2). log4j-1.2.8.jar (U can choose any version of log4j according to your requirement)
    Example Location: *"C:\bea922\user_projects\domains\Test_Domain\lib"* Here u need to place those two Jars
    Thanks
    Jay SenSharma
    http://middlewaremagic.com/weblogic/?page_id=2261 (Middleware Magic Is Here)

  • Migrate Oracle Apps Forms to J2EE

    Hi,
    I need to migrate Oracle Apps(11i) Forms to J2EE.
    I went through Oracle Partners who provide these migration tools but none provides trial version to test/use.
    How do I migrate forms.
    Or is there any way so that I can replace forms with my custom screens?
    Need your help.

    Its probably too long an answer to write here but I always like to start with the WHY?
    The one thing that is fact is that this will cost you considerable time and effort so you have to be very clear on your reasons. Furthermore, there is no "magic bullet". There is no tool or solution that can "with one click" migrate your application - unless your application is Emp/Dept of course ;o)
    You also have to seriously consider the need (infact I would say REQUIREMENT) that any migration MUST rearchitect. A Forms app and a J2EE app are very different, if you don't re-architect then you are re-implementing Forms in Java (in which case, why bother).
    If you go to http://otn.oracle.com/goto/formsmodernize there is information that we in Oracle see as the most likely approach to succeed - which is retain an investment in Forms while you build up skills/services/functionality in your new system
    I'd suggest spending a couple of hours reading this information and then if you have further questions you can come back to us.
    Regards
    Grant

  • Using Weblogic to Deploy Simple Flex App

    Hi,
       I am trying to deploy a simple Flex application in a weblogic8.1  server , so that I can use it locally.
    Can any one please guide me where and how I have to deploy my flex app .
    I am pretty new to this can any body provide me a guide or walk through step wise for me.
    More over What is the url I need to give in the browser to access the flex app I deploy in the Weblogic server.
    (At present I am using the IIS -- just copying the .swf file and wrapper html page in to the C:\Inetpub\wwwroot and giving http://localhost/test.html
    in the browser to access it) ---  How do I do this using Weblogic 8.1
    thanks
    Nash

    Hi again Nash,
    the stuff I am doing at present is not yet permitted to be publicly available, but the principles are very straightforward. Remember that WebLogic is primarily concerned with server-side functionality and Flex with client-side, so there is not really a great deal of overlap. The place where your Flex instantiation code will sit is in one or other JSP, using code very like the templates that Adobe generate. The only thing you have to do is ensure that your JSP (or the controller/code files behind it) generate HTML that contains the necessary. I tend to use the Apache Beehive libraries for UI stuff, but from vague memory I don't think these were around in WL8 - however, it doesn't really matter what tag library you prefer as all you are doing is generating HTML that looks like the usual JavaScript calls to AC_FL_RunContent (or swfobject if you are using that method). Basically, just take the Adobe-generated template and wrap the necessary bits and pieces round the edge to make it a proper JSP.
    When you need to make calls to get functionality, just use something like
                        service = new HTTPService();
                        separator_date = new Date();
                        service.url = "get_tool_list.jsp?sep=" + separator_date.valueOf();
                        service.addEventListener(FaultEvent.FAULT , fault_handler);
                        service.addEventListener(ResultEvent.RESULT, resultHandler);
                        service.resultFormat = "text";
                        CursorManager.setBusyCursor();
                        service.requestTimeout = WEB_SERVICE_TIMEOUT;
                        service.send();
    and then inside get_tool_list.jsp (or whatever...) do the server-side functionality you need, and return the result in a suitable format that the Flex resultHandler method can then interpret and make use of.
    Hope that helps,
    Richard

  • Using  Weblogic app environment in Visual Age

    Hi,
              I am using Weblogic as my test environment in Visual Age. I am getting alone
              well with servlet and beans. But I am having enormous problem with jsp. Does
              any body know how to configure weblogic test environment in Visual age to
              use bean tag in JSP (the JSP cannot locate the beans although the classpath
              has set to the project_resource/project Name).
              Help will be highly appreciated
              Duke
              

    "Michael Girdley" <[email protected]> wrote in message
              news:396a80d4$[email protected]..
              > JSP integration is not supported with Weblogic and VisualAge. This is
              > because VisualAge supports a back level revision of the JSP specification
              > and has also created their JSP container to be tightly integrated with
              > VisualAge.
              I don't understand this at all.
              My VisualAge has no notion of JSP (professional), that all came after I
              imported all of
              the weblogic stuff. So what does "VA supports a back level revision of JSP
              spec" actually
              mean?
              Also, "has created their JSP container to be tightly integrated with VA".
              There is no
              JSP container to speak of except for that which weblogic provides. Perhaps
              you are
              referring to some Websphere/VA environment?
              All in all, the integration is just about wonderful. Is there a good reason
              why JSP is not
              supported? Seeing what VA does with the WebSphere environment, I believe
              that the IDE
              environment is capable of dynamically reloading classes that have been
              generated etc.
              The basic question is: Why doesn't the VA environment support JSP's? If the
              answer is:
              "we haven't implemented it yet" then I understand, (and will ask when it
              will be:-) ).
              Questioningly,
              Jon
              

  • 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

  • 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

  • Using weblogic security roles in authentication: weblogic 9

    Hi All,
    I am trying to create a simple application which uses declarative authorization configured in web.xml. I use the simple form based authentication. While trying to deploy my application, I get the error:
    weblogic.management.DeploymentException: [HTTP:101168]The security-role-assignment references an invalid security-role: LTVORole.
    But I have defined the role LTVORole in weblogic using the administrator console.
    below are the details of what I have done:
    Web.xml:
    ========
    <?xml version='1.0' encoding='UTF-8'?>
    <j2ee:web-app xmlns:j2ee="http://java.sun.com/xml/ns/j2ee">
      <j2ee:welcome-file-list>
        <j2ee:welcome-file>login.jsp</j2ee:welcome-file>
        <j2ee:welcome-file>index.html</j2ee:welcome-file>
        <j2ee:welcome-file>index.htm</j2ee:welcome-file>
      </j2ee:welcome-file-list>
      <j2ee:login-config>
        <j2ee:auth-method>FORM</j2ee:auth-method>
        <j2ee:form-login-config>
          <j2ee:form-login-page>/login.jsp</j2ee:form-login-page>
          <j2ee:form-error-page>/error.jsp</j2ee:form-error-page>
        </j2ee:form-login-config>
      </j2ee:login-config>
    <security-constraint>
      <display-name>checkAccountConstraint</display-name>
    <web-resource-collection>
      <web-resource-name>checkAccountCollection</web-resource-name>
            <url-pattern>test.jsp</url-pattern>
            <http-method>GET</http-method>
            <http-method>POST</http-method>
      </web-resource-collection>
      <auth-constraint>
            <role-name>LTVORole</role-name>
      </auth-constraint>
      </security-constraint>
    </j2ee:web-app>Weblogic.xml
    ===========
    <?xml version="1.0" encoding="UTF-8"?>
    <ns:weblogic-web-app xmlns:ns="http://www.bea.com/ns/weblogic/90">
      <security-role-assignment>
        <role-name>LTVORole</role-name>
       <externally-defined/>
      </security-role-assignment>
    </ns:weblogic-web-app>I have created the role in weblogic in the menu
    security realms > myrealm > roles and policies > Global Roles > roles > LTVORole
    Is it the right way to define a role?
    Please help me find where I am going wrong.
    Thanking you all in advance,
    Gireesh

    Hi All,
    I am trying to create a simple application which uses declarative authorization configured in web.xml. I use the simple form based authentication. While trying to deploy my application, I get the error:
    weblogic.management.DeploymentException: [HTTP:101168]The security-role-assignment references an invalid security-role: LTVORole.
    But I have defined the role LTVORole in weblogic using the administrator console.
    below are the details of what I have done:
    Web.xml:
    ========
    <?xml version='1.0' encoding='UTF-8'?>
    <j2ee:web-app xmlns:j2ee="http://java.sun.com/xml/ns/j2ee">
      <j2ee:welcome-file-list>
        <j2ee:welcome-file>login.jsp</j2ee:welcome-file>
        <j2ee:welcome-file>index.html</j2ee:welcome-file>
        <j2ee:welcome-file>index.htm</j2ee:welcome-file>
      </j2ee:welcome-file-list>
      <j2ee:login-config>
        <j2ee:auth-method>FORM</j2ee:auth-method>
        <j2ee:form-login-config>
          <j2ee:form-login-page>/login.jsp</j2ee:form-login-page>
          <j2ee:form-error-page>/error.jsp</j2ee:form-error-page>
        </j2ee:form-login-config>
      </j2ee:login-config>
    <security-constraint>
      <display-name>checkAccountConstraint</display-name>
    <web-resource-collection>
      <web-resource-name>checkAccountCollection</web-resource-name>
            <url-pattern>test.jsp</url-pattern>
            <http-method>GET</http-method>
            <http-method>POST</http-method>
      </web-resource-collection>
      <auth-constraint>
            <role-name>LTVORole</role-name>
      </auth-constraint>
      </security-constraint>
    </j2ee:web-app>Weblogic.xml
    ===========
    <?xml version="1.0" encoding="UTF-8"?>
    <ns:weblogic-web-app xmlns:ns="http://www.bea.com/ns/weblogic/90">
      <security-role-assignment>
        <role-name>LTVORole</role-name>
       <externally-defined/>
      </security-role-assignment>
    </ns:weblogic-web-app>I have created the role in weblogic in the menu
    security realms > myrealm > roles and policies > Global Roles > roles > LTVORole
    Is it the right way to define a role?
    Please help me find where I am going wrong.
    Thanking you all in advance,
    Gireesh

  • With out using Weblogic libraries to maintain the same functionality

    Hi,
    Please tell the solution of my problem.Here application developed in Weblogic,now we are migrating that applicationin jboss.Here one java servlet program is there which is using Weblogic libraries to get the connection pool .
    How can change the code without using Weblogic libraries to maintain the same funtionality. Is there any alternate method to get the connection pools in Jboss.
    Here I am attaching the code ,please go througth the code and provide me the correct solution.
    package gsk.servlets;
    import java.io.*;
    import java.sql.Connection;
    import java.sql.Statement;
    import java.sql.ResultSet;
    import javax.naming.Context;
    import javax.naming.NamingException;
    import javax.management.*;
    import javax.management.InstanceNotFoundException;
    import javax.management.InvalidAttributeValueException;
    import javax.management.Notification;
    import javax.servlet.*;
    import javax.servlet.http.*;
    //Below lines are commnented by Anupama on 29-09-05 to avoid using Weblogic libraries.
    //import weblogic.jndi.Environment;
    //import weblogic.management.MBeanHome;
    //import weblogic.management.MBeanCreationException;
    //import weblogic.management.*;
    //import weblogic.management.runtime.*;
    //import weblogic.management.configuration.*;
    //import weblogic.management.RemoteNotificationListener;
    //import weblogic.management.logging.WebLogicLogNotification;
    //import javax.management.Notification.*;
    //below lines are added by Anupama T on 29-09-05 to run the same functionality without using Weblogic libraries
    import org.jboss.management.*;
    import org.jboss.jdbc.*;
    import org.jboss.naming.*;
    import org.jboss.management.j2ee.MBean;
    import javax.management.AttributeChangeNotification;
    import javax.management.JMException;
    import javax.management.MalformedObjectNameException;
    import javax.management.MBeanServer;
    import javax.management.NotificationListener;
    import javax.management.ObjectName;
    import org.jboss.logging.Logger;
    import org.jboss.system.ServiceMBean;
    import gsk.adip.portal.GKMProperties;
    import gsk.adip.dbconnectionservice.DatabaseConnector;
    * @author jjc18400
    * The ConnectionsManager class acts as a Servlet that listens and
    * responds to events that are thrown by WebLogic MBeans. In particular,
    * it listens for failures in WebLogic connection pools, and attempts to
    * restore these pools.
    public class ConnectionsManager extends HttpServlet implements NotificationListener {
         private static Context ctx;
         private static MBean managedHome;
         private static MBean adminHome;
         private static String SERVER_NAME;
         private static String DOMAIN_NAME;
         private static MBeanServer myServer;
         private JDBCConnectionPoolRuntimeMBean connectionPoolMBean;
         private JDBCConnectionPoolMBean jdbcConnPoolMBean;
         private JDBCConnectionPoolMBean myPool;
         private static ResultSet rset = null;
         public void init(ServletConfig config) throws ServletException {
              super.init(config);
              System.out.println("Initializing the ConnectionsManager servlet.");
              SERVER_NAME = GKMProperties.getProperty("GKM_SERVER_NAME");
              DOMAIN_NAME = GKMProperties.getProperty("DOMAIN_NAME");
              findMBeans();
              testConnectionPool("GENNETConnectionPool");
              try {
                   //findConnPool("GENNETConnectionPool").addNotificationListener(this, null, null);
                   RemoteMBeanServer rmbs = adminHome.getMBeanServer();
                   WebLogicObjectName oname =
                        new WebLogicObjectName("TheLogBroadcaster", "LogBroadcasterRuntime", DOMAIN_NAME, SERVER_NAME);
                   rmbs.addNotificationListener(oname, this, null, null);
              catch (IllegalArgumentException e) {}
              catch (MalformedObjectNameException e) {}
              catch (InstanceNotFoundException e) {}          
         public void handleNotification(Notification notification, Object obj) {
              WebLogicLogNotification wln = (WebLogicLogNotification)notification;
              System.out.println("\nWebLogicLogNotification");
              System.out.println(" type = " + wln.getType());
              System.out.println(" message id = " + wln.getMessageId());
              System.out.println(" server name = " + wln.getServername());
              System.out.println(" timestamp = " + wln.getTimeStamp());
              System.out.println(" message = " + wln.getMessage() + "\n");
         private void testConnectionPool(String poolName) {
              JDBCConnectionPoolMBean aPool = findConnPool(poolName);
              JDBCConnectionPoolRuntimeMBean aRuntimeMBean = findRuntimeMBean(poolName);
              /*while(aRuntimeMBean.getPoolState()) {
                   try {
                        Thread.sleep(6000);
                        System.out.println("Thread is sleeping.");
                   catch (InterruptedException ie) {
              retargetConnPool(aPool);
         private JDBCConnectionPoolRuntimeMBean findRuntimeMBean(String aPoolName) {
              JDBCConnectionPoolRuntimeMBean aRuntimeMBean = null;
              if (managedHome != null) {
                   try {
                        aRuntimeMBean = (JDBCConnectionPoolRuntimeMBean)managedHome.
                                  getRuntimeMBean(aPoolName, "JDBCConnectionPoolRuntime");
                   catch (InstanceNotFoundException e) {
                        System.out.println("Unable to find the JDBCConnectionPoolRuntimeMBean: " + e);
                        aRuntimeMBean = null;
              return aRuntimeMBean;
         private JDBCConnectionPoolMBean findConnPool(String poolName) {
              if (adminHome != null) {
                   try {
                        myPool = (JDBCConnectionPoolMBean)adminHome.getMBean(poolName, JDBCConnectionPoolMBean.class);
                   catch (InstanceNotFoundException e) {
                        System.out.println("Unable to find the JDBCConnectionPoolMBean: " + e);
                        myPool = null;
              return myPool;
         private void retargetConnPool(JDBCConnectionPoolMBean aPool) {
              //System.out.println("The connection pool: " + aPool.toString() + " is not responding.\nAttempting to retarget the pool...");
              try {
                   System.out.println("Attempting to remove " + myServer.toString() + " from the connection pool target list.");
                   aPool.removeTarget(myServer);
                   System.out.println("Removal successful: " + aPool.getTargets().toString());
                   aPool.addTarget(myServer);
                   System.out.println("Addition successful: " + aPool.getTargets().toString());
              catch (InvalidAttributeValueException e) {
                   System.out.println(e.toString());
              catch (DistributedManagementException e) {
                   System.out.println(e.toString());
         public void doPost(HttpServletRequest req, HttpServletResponse resp)
                   throws ServletException, IOException {
              String poolName = (String)req.getParameter("poolName");
              String dataSource = (String)req.getParameter("dataSource");
              //System.out.println("req.getAttribute(poolName) is: " + poolName);
              //System.out.println("req.getAttribute(dataSource) is: " + dataSource);
              String message = runTestQuery(dataSource);
              getConnectionPoolMBean(poolName);
              resp.setContentType("text/html");
              PrintWriter out = resp.getWriter();
              out.println("<html>");
              out.println(" <head><title>The ConnectionsManager Responds:</title></head>");
              out.println(" <body>");
              out.println(" <h1>" + message + "</h1>");
              out.println(" </body>");
              out.println("</html>");
         public void destroy() {
              System.out.println("Destroying the ConnectionsManager servlet.");
         public String getServletInfo() {
              return "This servlet monitors and corrects errors in WebLogic connection pools.";
         /**private void runTests() {
              while (false) {
                   rset = testConnection();
                   if (rset == null) {
                        resetConnectionPool();                    
                   try {
                        wait();
                   catch (InterruptedException e) {}
         private String runTestQuery(String dataSource) {
              String statusMessage = "";
              Connection conn = null;
              Statement stmt = null;
              ResultSet rset = null;
              //String aPoolName = "GENNETConnectionPool";
              String aSql = "select * from dual where 1 = 1";
              try {
                   conn = DatabaseConnector.getDatabaseConnection(dataSource);
                   System.out.println("Established database connection.");
                   if (conn != null) {
                        conn.setAutoCommit(false);
                        stmt = conn.createStatement();
                        rset = stmt.executeQuery(aSql);
                        statusMessage = "The connection \'" + dataSource + "\' is OK.";
              catch (Exception e) {
                   try {
                        conn.rollback();
                   catch (Exception e1) {}
                   e.printStackTrace();
                   statusMessage = "The connection \'" + dataSource + "\' has failed.\n" + e.toString();
              finally {
                   try {
                        if (stmt != null) stmt.close();
                        if (conn != null) conn.close();
                   catch (Exception e) {
                        e.printStackTrace();
                   return statusMessage;
         public void resetConnectionPool() {
         private void findConnPoolRuntimeMBean(String poolName) {
              try {
                   connectionPoolMBean = (JDBCConnectionPoolRuntimeMBean)managedHome.getRuntimeMBean(poolName, "JDBCConnectionPoolRuntime");
              catch (InstanceNotFoundException e) {
                   System.out.println("Unable to find the JDBCConnectionPoolRuntimeMBean: " + e);
         private void findMBeans() {
              Environment env = new Environment();
              try {
                   ctx = env.getInitialContext();
                   managedHome = (MBeanHome)ctx.lookup(MBeanHome.JNDI_NAME + "." + SERVER_NAME);
                   System.out.println(MBeanHome.JNDI_NAME + "." + SERVER_NAME + " -- managedHome found successfully.");
                   adminHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
                   System.out.println(MBeanHome.ADMIN_JNDI_NAME + " -- adminHome found successfully.");
                   myServer = (ServerMBean)adminHome.getMBean(SERVER_NAME, ServerMBean.class );
                   System.out.println(MBeanHome.ADMIN_JNDI_NAME + " -- " + SERVER_NAME + " instance found successfully.");
                   ctx.close();
              catch (NamingException e) {
                   System.out.println("Naming Exception: " + e);
                   managedHome = null;
                   adminHome = null;
              catch (InstanceNotFoundException e) {
                   System.out.println("Unable to find the JDBCConnectionPoolMBean: " + e);
         public String displayHomeName() {
              getConnectionPoolMBean("GENNETConnectionPool");
              if (managedHome != null) {
                   return new String("MBeanHome found successfully.");
              else return new String("MBeanHome not found.\nSee WL Console for error.");
         private void getConnectionPoolMBean(String poolName) {
              String thisPoolName = poolName;
              connectionPoolMBean = null;
              if (managedHome != null) {
                   try {
                        connectionPoolMBean =
                             (JDBCConnectionPoolRuntimeMBean)managedHome.getRuntimeMBean(thisPoolName, "JDBCConnectionPoolRuntime");
                        if (connectionPoolMBean != null) {
                             System.out.println("JDBCConnectionPoolRuntime found successfully.");
                             System.out.println("connectionPoolMBean.toString() is: " + connectionPoolMBean.toString());
                             System.out.println("connectionPoolMBean.getFailuresToReconnectCount() is: " + connectionPoolMBean.getFailuresToReconnectCount());
                             System.out.println("connectionPoolMBean.getPoolState() is: " + connectionPoolMBean.getPoolState());
                   catch (InstanceNotFoundException e) {
                        System.out.println("Unable to find the JDBCConnectionPoolRuntimeMBean: " + e);
                        connectionPoolMBean = null;
              // Obtain MBeanHome for the administration server.
              /*JDBCConnectionPoolMBean mbean = (JDBCConnectionPoolMBean)home.
                        getConfigurationMBean(poolName, "JDBCConnectionPoolConfig");
              mbean.setConnLeakProfilingEnabled(true);
              mbean.setSqlStmtParamLoggingEnabled(true);
              mbean.setSqlStmtMaxParamLength(maxLen);*/
              /*try {
                   mypool = (JDBCConnectionPoolMBean)mbh.getMBean( "mypool",
                   JDBCConnectionPoolMBean.class );
              catch( javax.management.InstanceNotFoundException e ) {
                   mypool = (JDBCConnectionPoolMBean) mbh.createAdminMBean( "mypool",
                        "JDBCConnectionPool", "mydomain" );
                   mypool.addTarget( myserver );
                   mypool.setDriverName( "org.gjt.mm.mysql.Driver" );*/
              if (adminHome != null) {
                   try {
                        myPool = (JDBCConnectionPoolMBean)adminHome.getMBean(poolName, JDBCConnectionPoolMBean.class);
                   catch (InstanceNotFoundException e) {
                        System.out.println("Unable to find the JDBCConnectionPoolMBean: " + e);
              if (myPool != null) {
                   //System.out.println("myPool.getMaxCapacity() is: " + myPool.getMaxCapacity());
                   try {
                        myPool.setMaxCapacity(10);
                        System.out.println("Before: myPool.getMaxCapacity() is: " + myPool.getMaxCapacity());
                        myPool.setMaxCapacity(100);
                        System.out.println("After: myPool.getMaxCapacity() is: " + myPool.getMaxCapacity());
                   catch (InvalidAttributeValueException e) {
                        System.out.println("Max Capacity is an invalid value.");
                   //System.out.println("myPool.getMaxCapacity() is: " + myPool.getMaxCapacity());
    }

    Hy, i've got the same problem as you. Did you find out a solution.
    If so, please contact me. Thanks a lot.
    Lorenzo

  • Cannot start application deployed using Weblogic console after stop

    Hello all,
    I have deployed an ear file using Weblogic console. If the app. is running, I can press stop and get the 404 error...after that I press start, and get a 503 error. Right after the app is deployed, and started, it always comes up fine. But when the application is running, I must click stop, start, stop, start to get the app to start.
    To start the app. I select, start and then "servicing all requests". To stop the app, I select stop and then "Force stop now". I have implemented a subclass of ServletContextListener to handle the start and stop. These methods do get called.
    The 503 did not cause any errors to be found in the weblogic.log, stdout.log or access.log.
    Does anyone have an idea how to start the app after it is stopped the first time?
    Thanks in advance.
    -PD
    Edited by pauladecker at 10/01/2007 1:47 PM

    Hi,
    As you see this error.
    [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.webcenter.framework, Specification-Version: 11.1.1, exact-match: false], [Extension-Name: oracle.sdp.client, exact-match: false].
    there is some miss match in library reference.
    Please check with your weblogic-application.xml file.
    Regards,
    Kal

  • 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>

  • 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

  • Using weblogic.Server to create domains

    Not sure this is the right group for this question....
    I am reading some weblogic docs on creating a domain using weblogic.Server (http://e-docs.bea.com/wls/docs81/admin_ref/cli_tasks.html#1331827).
    For the most part it has worked as expected and I find it preferable to using
    the domain cfg wizard. However, is there a way to use a template jar like you
    can with the config wizard, for instance any of the jars in the
    $WL_HOME/common/templates/domains/

    Hello Jay, thanx for ur help... this time i didnt get the args missing error but i have this one about "can't overwrite"
    mauro@MacBookPro:HelloWorldEAR $ java -classpath /Users/mauro/beaWS102/wlserver_10.0/server/lib/weblogic.jar weblogic.BuildXMLGen /Users/mauro/Documents/WLprojects/HelloWorldEAR
    Can't overwrite cause
    mauro@MacBookPro:HelloWorldEAR $ cd ..
    mauro@MacBookPro:WLprojects cursor$ sudo java -classpath /Users/mauro/beaWS102/wlserver_10.0/server/lib/weblogic.jar weblogic.BuildXMLGen /Users/mauro/Documents/WLprojects/HelloWorldEAR
    Can't overwrite cause
    mauro@MacBookPro:WLprojects cursor$ cd HelloWorldEAR/
    mauro@MacBookPro:HelloWorldEAR $ ls
    APP-INF META-INF appUtils bin helloWorldEJB helloWorldWebApp src
    macbook-de-cursor:HelloWorldEAR cursor$ cd ..
    mauro@MacBookPro:WLprojects $ sudo java -classpath /Users/mauro/beaWS102/wlserver_10.0/server/lib/weblogic.jar weblogic.BuildXMLGen -file build.xml /Users/mauro/Documents/WLprojects/HelloWorldEAR
    Can't overwrite cause
    Do u know something about this message?? I really need to set up this thig to be able to start my own project :P Thanx in advance
    Best regards,
    Mauro
    ==========================================================
    Solution
    Ok, i make it work!! I have in my develop structure a helloWorldWebContent/META-INF/ and here i had a web.xml and a weblogic.xml
    The weblogic.xml file cause problems... i deleted and it works
    I was following this tutorial
    http://download.oracle.com/docs/cd/E13222_01/wls/docs100/programming/splitcreate.html#wp1098227
    and i create all those files...
    Dude, u have a great blog! Now it is in my bookmarks
    Edited by: mgaldames on 17-may-2010 7:20
    Edited by: mgaldames on 17-may-2010 7:21

Maybe you are looking for