OJMS Connection Factory Error

Hi,
(Platforms: OC4J developer preview 4, JDev 10.1.3 EA, Database :Oracle 10.1.0 )
I have tried to implement the JMS provider (OJMS) according to the following document :
http://www.oracle.com/technology/sample_code/tech/java/codesnippet/jms/datasources/ResourceProvider.html
In my client code while I try to get the queue by :
queue = (Queue)jndiContext.lookup("java:comp/resource/TestRP/Queues/RPQueue");
there is no problem. But when I try to get connection factory by :
queueConnectionFactory = (QueueConnectionFactory) jndiContext.lookup("java:comp/resource/TestRP/QueueConnectionFactories/RPTable");
it fails and gives the following exception:
05/11/28 11:40:19 javax.naming.NamingException: Lookup error: java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910; nested exception is:
     java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910 [Root exception is java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910]
05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:68)
05/11/28 11:40:19      at javax.naming.InitialContext.lookup(InitialContext.java:351)
05/11/28 11:40:19      at BServlet.insertToQueue(BServlet.java:224)
05/11/28 11:40:19      at BServlet.doPost(BServlet.java:199)
05/11/28 11:40:19      at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
05/11/28 11:40:19      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
05/11/28 11:40:19      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:846)
05/11/28 11:40:19      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:397)
05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:245)
05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:231)
05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketAcceptHandler.access$1000(ServerSocketAcceptHandler.java:33)
05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:820)
05/11/28 11:40:19      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
05/11/28 11:40:19      at java.lang.Thread.run(Thread.java:595)
05/11/28 11:40:19 Caused by: java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910
05/11/28 11:40:19      at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:100)
05/11/28 11:40:19      at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:83)
05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientConnection.waitForJndiResponse(RMIClientConnection.java:341)
05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:158)
05/11/28 11:40:19      at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:235)
05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:55)
05/11/28 11:40:19      ... 18 more
Any idea?
Thanks,

Hi Brian,
I am also facing the same issue in SAP PI NWA for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file. we are on SAP PI 7.11 sp06....
error details : CF_XX_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
The logs details : Can not set authentication user store "null" in security context "CF_XX_XX0" for connector "CF_XX_XX0" in application "sap.com/tc~sapjra".".
could you share info, how your issue got solved..
Regards
ashutosh r

Similar Messages

Application Deployment in Managed Node Failed with the error - ERROR   - Caught exception while looking up Connection Factory with JNDI Name: java:comp/env/eis/PRAdapterConnectionFactory, javax.naming.ServiceUnavailableException [Root exception is java.ne

2013-06-24 21:16:28,551 [bxapp2.healthnet.com] [ STANDARD] [                    ] (l.access.RuleCandidateIterator) INFO    - Single candidate rule resolution optimization is enabled
Error retrieving JNDI initial context:
2013-06-24 21:16:28,952 [bxapp2.healthnet.com] [ STANDARD] [                    ] (    pegarules.resadap.RAClient) ERROR   - Caught exception while looking up Connection Factory with JNDI Name: java:comp/env/eis/PRAdapterConnectionFactory, javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:34)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at com.pega.pegarules.priv.util.JNDIUtil.getInitialContext(JNDIUtil.java:106)
at com.pega.pegarules.priv.util.JNDIUtil.lookupUsingRealContextClassLoader(JNDIUtil.java:128)
at com.pega.pegarules.resadap.RAClient.init(RAClient.java:102)
at com.pega.pegarules.resadap.RAClient.<init>(RAClient.java:84)
at com.pega.pegarules.resadap.RAClientContainer.get(RAClientContainer.java:47)
at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:146)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.callRAClient(ListenerWrapper.java:358)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.launchListener(ListenerWrapper.java:233)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startOneListener(ListenerStateManagerImpl.java:713)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startServiceTypeListeners(ListenerStateManagerImpl.java:464)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startListenerType(ListenerStateManagerImpl.java:423)
at com.pega.pegarules.integration.engine.internal.PRIntegrationEngineProviderImpl.initServices(PRIntegrationEngineProviderImpl.java:166)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.initServices(PREnvironment.java:620)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:522)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
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:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.net.UnknownHostException: Unknown protocol: 'TCP'
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:216)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
... 94 more
2013-06-24 21:16:28,952 [bxapp2.healthnet.com] [ STANDARD] [                    ] (tener.ListenerStateManagerImpl) ERROR   - Unexpected exception.
java.lang.NullPointerException
at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:150)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.callRAClient(ListenerWrapper.java:358)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.launchListener(ListenerWrapper.java:233)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startOneListener(ListenerStateManagerImpl.java:713)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startServiceTypeListeners(ListenerStateManagerImpl.java:464)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startListenerType(ListenerStateManagerImpl.java:423)
at com.pega.pegarules.integration.engine.internal.PRIntegrationEngineProviderImpl.initServices(PRIntegrationEngineProviderImpl.java:166)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.initServices(PREnvironment.java:620)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:522)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
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:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
2013-06-24 21:16:28,956 [bxapp2.healthnet.com] [ STANDARD] [                    ] (          internal.async.Agent) INFO    - Agents will be executed via the enterprise tier.
2013-06-24 21:16:28,956 [bxapp2.healthnet.com] [ STANDARD] [                    ] (          internal.async.Agent) INFO    - Passivation will be done on a per-page basis.
2013-06-24 21:16:30,023 [bxapp2.healthnet.com] [ STANDARD] [                    ] (    pegarules.resadap.RAClient) ERROR   - Caught exception while looking up Connection Factory with JNDI Name: java:comp/env/eis/PRAdapterConnectionFactory, javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:34)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at com.pega.pegarules.priv.util.JNDIUtil.getInitialContext(JNDIUtil.java:106)
at com.pega.pegarules.priv.util.JNDIUtil.lookupUsingRealContextClassLoader(JNDIUtil.java:128)
at com.pega.pegarules.resadap.RAClient.init(RAClient.java:102)
at com.pega.pegarules.resadap.RAClient.<init>(RAClient.java:84)
at com.pega.pegarules.resadap.RAClientContainer.get(RAClientContainer.java:47)
at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:146)
at com.pega.pegarules.monitor.internal.UsageDaemonImpl.initialize(UsageDaemonImpl.java:546)
at com.pega.pegarules.session.internal.async.Agent.start(Agent.java:1400)
at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.startNode(PRNodeImpl.java:1520)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:533)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
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:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.net.UnknownHostException: Unknown protocol: 'TCP'
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:216)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
... 84 more
2013-06-24 21:16:30,038 [bxapp2.healthnet.com] [ STANDARD] [                    ] (      etier.impl.EngineStartup) ERROR   - PegaRULES initialization failed. Server: pg-sbxapp2.healthnet.com
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:387)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
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:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: com.pega.pegarules.pub.PRRuntimeException: Method Invocation exception
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1045)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
... 60 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
... 62 more
Caused by: java.lang.NullPointerException
at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:150)
at com.pega.pegarules.monitor.internal.UsageDaemonImpl.initialize(UsageDaemonImpl.java:546)
at com.pega.pegarules.session.internal.async.Agent.start(Agent.java:1400)
at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.startNode(PRNodeImpl.java:1520)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:533)
... 67 more
2013-06-24 21:16:30,051 [bxapp2.healthnet.com] [ STANDARD] [                    ] (      etier.impl.EngineStartup) INFO    - PegaRULES initialization failed. Server: pg-sbxapp2.healthnet.com
2013-06-24 21:16:30,164 [bxapp2.healthnet.com] [ STANDARD] [                    ] (ervlet.WebAppLifeCycleListener) ERROR   - Enterprise tier failed to initialize properly, PegaRULES not available
2013-06-24 21:16:30,190 [bxapp2.healthnet.com] [ STANDARD] [                    ] (ervlet.WebAppLifeCycleListener) INFO    - Web Tier initialization is complete.
<Jun 24, 2013 9:16:30 PM PDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Jun 24, 2013 9:16:30 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Jun 24, 2013 9:16:30 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Jun 24, 2013 9:16:30 PM PDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 167.238.162.41:8008 for protocols iiop, t3, ldap, snmp, http.>
<Jun 24, 2013 9:16:30 PM PDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "pegamanaged2" for domain "sbxdomain8" running in Production Mode>
<Jun 24, 2013 9:16:31 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Jun 24, 2013 9:16:31 PM PDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

Greetings,
javax.naming.NameNotFoundException. Root exception is
org.omg.CosNaming.NamingContextPackage.NotFound
=================
Below is the line of my LoginServlet class which is
referred to in the stack trace - Object object =
context.lookup
                    ( "java:comp/env/ejb/WarehouseClerk" );The root of the naming context is 'java:comp/env' and this is where lookup automatically begins for EJBs and resources. IOW, by specifying "java:comp/env/ejb/WarehouseClerk" as the EJB lookup name the server is actually treating this as "java:comp/env/java:comp/env/ejb/WarehouseClerk". Specify only the ejb context ("ejb/WarehouseClerk") in your lookup and you should be fine.
Any help would be most appreciated.
SeanRegards,
Tony "Vee Schade" Cook

Error when creating a new JMS connection factory in GlassFish V3 b57

When I use the admin console and try to create a new JMS connection factory in GlassFish V3 b57, the operation fails with the error message
An error has occurred: Can't find ConfigModel.Property for attr -connection-validation-required on interface com.sun.enterprise.config.serverbeans.ConnectorConnectionPool
Should I better report this in the GlassFish news forum (http://forums.java.net/jive/forum.jspa?forumID=56&start=0)?
p.s. I launch the admin console from within NetBeans 6.7.1 (the server started before the IDE). WIth version b 56, creating a JMS connection factory worked fine.
Best regards,
Michael Justin

This bug does not apear in the nightly build (b58) now so everything looks fine again.
Greetings,
Michael

Error saving JCA Connection factory in PI NWA

Hi All,
I am facing an issue in SAP PI NWA for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file. we are on SAP PI 7.11 sp06....
error details : CF_XD1_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
The logs details : com.sap.engine.services.connector.exceptions.ConnectorException: Connector remote administration failed, reason: "Can not set authentication user store "null" in security context "CF_XD1_180" for connector "CF_XD1_180" in application "sap.com/tc~sapjra".".
at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.addComponent(ConnectorContainerImpl.java:1005
i posted this in SAP PI forum also...
Error saving connection factory
Regards
ashutosh r

Hello Carme,
From the error , I can see that the name of the JCA Connection Factory that you are trying to create in NWA is: "MRD_300".
This beautiful blog by William will surely help you rectify the problem.
/people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
Kindly check if you have done the following in your configuration:
1. Copy and create new dependent JCA Connection Factory from the JCA resource: "SAPJavaResourceAdapter15"
2. You have to go to the "Configuration Properties" tab (and not Security tab) of your JCA connection Factory (MRD_300) to enter the credentials that will be used by this CF. Make sure that you enter the details properly. Eg. In your case, just check if the password is entered.
3. Also, check if the JCA resource "SAPJavaResourceAdapter15" is up and running (green traffic light). Else, restart the corresponding Java Service from NWA -> Operations Management -> Start & Stop -> Java Services
I hope this should solve your problem.
Regards, Gaurav.

Error saving connection factory

I was trying to create a JCA connection factory so that I can use the user module to convert IDOCs to flat file. But I was encountering this problem when saving
Saving JCA Connection Factory: CF_ID1_800 failed due to: Can not add connection factory
I use NWA_SUPERADMIN role.. But seems like even that can't save it correctly.
THanks

Hi Brian,
I am also facing the same issue in SAP PI NWA for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file. we are on SAP PI 7.11 sp06....
error details : CF_XX_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
The logs details : Can not set authentication user store "null" in security context "CF_XX_XX0" for connector "CF_XX_XX0" in application "sap.com/tc~sapjra".".
could you share info, how your issue got solved..
Regards
ashutosh r

Error : Connection factory has been stopped

Hi ,
i Have a JPA/Toplink application to be depolyed on OAS 10.1.3.3 , i defined a DataSource on the Application Server , but iam getting this error when iam trying to run my application :
Caused by: java.sql.SQLException: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection
factory has been stopped.
at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:259)
at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:142)
at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:127)
at oracle.toplink.essentials.jndi.JNDIConnector.connect(JNDIConnector.java:130)
Thanks
Message was edited by:
mr_jaber

well as always...nothing works like restart of the server. Issue resolved.

Error creating JCA connection factory in NWA

Hi,
I need to load an file with idoc content into a XML.
So parameter IDOCXmlToFlatConvertor is required and it's necessary to create a JCA Connection Factory in NWA.
I'm trying to do it using :
/people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
http://help.sap.com/saphelp_nwpi711/helpdata/en/b5/bd93642dd3410f90ebea702399fac4/frameset.htm
But, when i try to create a JCA Connection Factory in NWA, systems returns next error:
com.sap.engine.services.connector.exceptions.BaseDeploymentException: Can not set authentication user store "null" in security context "MRD_300" for connector "MRD_300" in application "sap.com/tc~sapjra".
at com.sap.engine.services.connector.deploy.util.security.SecurityUtils.deploySecurity(SecurityUtils.java:507)
However, creating JCA connection as indicated in this blog, security tab doesn't allow any change and field user store can't be modified.
How to do it?
Carme

Hello Carme,
From the error , I can see that the name of the JCA Connection Factory that you are trying to create in NWA is: "MRD_300".
This beautiful blog by William will surely help you rectify the problem.
/people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
Kindly check if you have done the following in your configuration:
1. Copy and create new dependent JCA Connection Factory from the JCA resource: "SAPJavaResourceAdapter15"
2. You have to go to the "Configuration Properties" tab (and not Security tab) of your JCA connection Factory (MRD_300) to enter the credentials that will be used by this CF. Make sure that you enter the details properly. Eg. In your case, just check if the password is entered.
3. Also, check if the JCA resource "SAPJavaResourceAdapter15" is up and running (green traffic light). Else, restart the corresponding Java Service from NWA -> Operations Management -> Start & Stop -> Java Services
I hope this should solve your problem.
Regards, Gaurav.

Error in looking up the JMS Connection Factory

          Hi,
          I am using weblogic6.1. I created a JMS Connection factory from administrator
          console with the name QueueConnectionFactory..But when i restart the server and
          try to look up that factory its giving an NameNotFoundException...This is the
          entry of the factory in config.xml
          <JMSConnectionFactory JNDIName="QueueConnectionFactory"
          Name="QueueConnectionFactory" Targets="myserver"/>
          But if i change reapply the target server to myserver from admin console whenever
          restart the server it works fine..
          I dont know where is the problem..Can u please update me on the problem if u people
          have any idea.
          The trace of the exceptions i got is as below:
          java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable to
          resolve QueueConnectionFactory. Resolved
          : '' Unresolved:'QueueConnectionFactory' ; remaining name ''
          java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable to resolve
          QueueConnectionFactory. Resolved: '' Unr
          esolved:'QueueConnectionFactory' ; remaining name ''
          Thanx
          Regards,
          Narayan


          Hi Zach,
          No, I dont think ur interpretation is right..Once the entry corresponding
          to JMS Connection Factory is there in config.xml, the server should automatically
          bind it at the time of booting.. right. Why should this administrator server come
          into the picture.
          Thanx
          "Zach" <[email protected]> wrote:
          >Don't know. Sounds like the admin server is not notifying JMS of the
          >changes under certain situations. You might post in the management.console
          >newsgroup.
          >
          >_sjz.
          >
          >"Narayan" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Hi,
          >> I am using weblogic6.1. I created a JMS Connection factory from
          >administrator
          >> console with the name QueueConnectionFactory..But when i restart the
          >server and
          >> try to look up that factory its giving an NameNotFoundException...This
          >is
          >the
          >> entry of the factory in config.xml
          >>
          >> <JMSConnectionFactory JNDIName="QueueConnectionFactory"
          >> Name="QueueConnectionFactory" Targets="myserver"/>
          >> But if i change reapply the target server to myserver from admin console
          >whenever
          >> restart the server it works fine..
          >> I dont know where is the problem..Can u please update me on the problem
          >if
          >u people
          >> have any idea.
          >> The trace of the exceptions i got is as below:
          >> ****************
          >> java.rmi.RemoteException: javax.naming.NameNotFoundException:
          >Unable to
          >> resolve QueueConnectionFactory. Resolved
          >> : '' Unresolved:'QueueConnectionFactory' ; remaining name ''
          >> java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable
          >to
          >resolve
          >> QueueConnectionFactory. Resolved: '' Unr
          >> esolved:'QueueConnectionFactory' ; remaining name ''
          >>
          >> **********************
          >>
          >> Thanx
          >> Regards,
          >> Narayan
          >>
          >>
          >
          >

Error in looking up JMS connection factory in cluster

          Hi,
          We have setup a JMS connection factory targeted to clustered servers. We currently
          have two physical servers defined in the cluster.
          When the clustered servers first comes up, we can't see the JMS connection factory
          in the JNDI tree of any of the clustered servers. We can see in the server log
          that factory is actually being started. Binding to the JNDI tree is not happening.
          Through Management console when we move the target of connection factory back
          and forth, then the problem is gone.
          Any pointers to the problem are welcome.
          P.S. We are using WL 7.0.1
          Thanks
          Nishchit


          Hi,
          We have setup a JMS connection factory targeted to clustered servers. We currently
          have two physical servers defined in the cluster.
          When the clustered servers first comes up, we can't see the JMS connection factory
          in the JNDI tree of any of the clustered servers. We can see in the server log
          that factory is actually being started. Binding to the JNDI tree is not happening.
          Through Management console when we move the target of connection factory back
          and forth, then the problem is gone.
          Any pointers to the problem are welcome.
          P.S. We are using WL 7.0.1
          Thanks
          Nishchit

JMS proxy and XA connection factory

Hi all,
I would like to ask you what is the best practice to adopt about the scenario described below.
A JMS proxy retrieves a message and processes it.
Any error could occurr during processing it and, in case of errors, the JMS proxy error handler publishes the message on ad hoc recovery destination D.
(later another app will check failed messages for fixing & republishing them into ALSB).
In that scenario we have the JMS proxy and the jms business service that, in case of errors, publishes on destination D.
Should the JMS proxy and the business service use both a XA connection factory in order to perform all the above steps in one transaction ?
Otherwise if the business service itself fails publishing on destination D, the message retrieved by the JMS proxy is lost and not re-delivered to the JMS proxy.
Or XA connection factory is not needed and could I use
Routing Options with exactly once or both are needed ?
Thanks
ferp

Hi all,
I did some tests and follow what I've achieved.
Scenario 1.
- Precondition
-- A JMS proxy with XA factory + Error Destination (MyRecoveryQueue)
-- A business service BS with XA factory that publishes into MyOutboundQueue
-- No "exactly once" routing option used calling BS
-- an error is forced in the pipeline
- Flow
-- proxy retrieves a message and try to publish it using BS
-- an error is forced in the pipeline:
--- transaction is rolled back, message redelivered to proxy
--- the message is posted to the error destination after all the retries failed
Scenario 2.
- Precondition
-- As 1. but no error is forced in the pipeline
-- the MyOutboundQueue destination queue is paused
- Flow
-- proxy retrieves a message and try to publish it using BS
-- BS fails to publish it on MyOutboundQueue (because it is paused)
--- transaction is rolled back, message redelivered to proxy
--- the message is posted to the error destination after all the retries failed
Scenario 2A.
- Precondition
-- As 2. with MyOutboundQueue paused and resumed
- Flow:
-- proxy retrieves a message and try to publish it using BS
-- BS fails to publish it on MyOutboundQueue (because it is paused)
--- transaction is rolled back, message redelivered to proxy
--- before all the retries failed the queue is resumed
--- BS succeeds to publish the message
Scenario 3.
- Precondition
-- A JMS proxy with NO XA factory + Error Destination
-- A business service BS with NO XA factory
-- No "exactly once" routing option used calling BS
-- an error is forced in the pipeline
- Flow
-- proxy retrieves a message and try to publish it using BS
-- an error is forced in the pipeline:
--- transaction is NOT rolled back, message NOT redelivered to proxy
-- so
--- no message delivered to MyOutboundQueue2 destination
--- no message delivered to MyRecoveryQueue2 destination
--- message consumed from MyQueue2 and now is lost!
To publish message into MyRecoveryQueue2 a proxy error handler has to be added and here added explicit publish to MyRecoveryQueue2.
But naturally in that case if in the proxy error handler, the explicit publish fails or any error occurrs no message is delivered to recovery queue.
So if I'm not using an XAFactory the message is auto-acknowledged as soon as it is read and I've to use XA factory if I want the message to be put back in the queue in case of errors and the retry to happen.
So both my proxy service and business service use an XA factory.
Regards
ferp

RMI How can a Client reconnect to a server after connection(any)-error

I have the following problem:
My RMI-Server runs for ever. In a batch-queue I have a procedure which looks periodly wether rmiregistry
and RMI-Server exists. On error both processes are killed and restarted.
My client as a simple example is displaying the server time. If any communication-problem with the
server exists, I need an automatic reconnect to the server. I accept that into the time distanz of the
error the display is frozen. Its unacceptable to restart the client !!.
The following example demonstates my test-example:
Server:
1. Start
2. waits for connecting (factory)
3. answer time-requests
Client:
1. Start
2. create a time class initially 1.jan.1970 00:00:00
3. Start a timer displaying the time class every second
4. start a timer connecting/reconnecting to the server and ask the servers actual time every second
PS. Is the server to stubil programmed, so that a hang can exists?
It would be nice, if anybody could answer me !!
The following sources work correctly without solving the problem of the reconnect:
////////////// Echo.java
package emi.server;
import java.rmi.*;
import java.util.*;
public interface Echo
extends Remote
public Date getTime() throws RemoteException;
////////////// EchoClient.java
package emi.server;
//import emi.utility.basics.*;
public class EchoClient
public static void main(String args[]) throws Exception
EchoClient echoclient1 = new EchoClient();
//Check the argument count
if (args.length != 1)
System.err.println("Usage: EchoClient <server> --> EXIT");
System.exit(0);
// all of time relevant things
Etim acttim = new Etim();
// displaying continous the time
EchoClientDisplay disp = new EchoClientDisplay(acttim);
disp.StartTimer();
// transfering continous the time from the server
EchoClientTransfer trans = new EchoClientTransfer(acttim, args[0]);
trans.StartTimer();
////////////// EchoClientDisplay.java
package emi.server;
import java.awt.event.*;
import javax.swing.*;
// displaying every 750 Milliseconds the value of the time
public class EchoClientDisplay implements ActionListener
private Timer tim;
private Etim tact;
public EchoClientDisplay(Etim tact)
tim = new Timer(750, this);
this.tact = tact;
public void StartTimer()
tim.setRepeats(true);
tim.setInitialDelay(5);
tim.start();
public void actionPerformed(ActionEvent e )
System.out.println(tact.toString());
////////////// EchoClientTransfer.java
package emi.server;
import java.rmi.Naming;
import java.rmi.RMISecurityManager;
import java.awt.event.*;
import javax.swing.Timer;
import java.util.Date;
// transferring the actual time from the server
public class EchoClientTransfer implements ActionListener
private Etim tact;
private String hostname;
private Timer tim;
private boolean init = false;
private Echo echoRef1 = null;
public EchoClientTransfer(Etim tact, String hostname)
this.tact = tact;
this.hostname = hostname;
this.tim = new Timer(500, this);
public void StartTimer()
tim.setRepeats(true);
tim.setInitialDelay(5);
tim.start();
public void actionPerformed(ActionEvent e )
//>>>>>>>>>>> this construction doesnt work correctly, its only good until the first
// network error
try
if( init == false )
// Create and install the security manager
System.setSecurityManager(new RMISecurityManager());
//get the remote factory object from the registry
String url = new String("rmi://"+ hostname +"/EchoFactory");
EchoFactory remoteFactory = (EchoFactory)Naming.lookup(url);
//get references to new EchoImpl instances
echoRef1 = remoteFactory.getEcho("User Meyer");
init = true;
if( init = true )
//make the remote calls
Date d = echoRef1.getTime();
tact.setDate(d);
catch(Exception ee)
System.out.println(ee.toString());
init = false;
//<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
////////////// EchoFactory.java
package emi.server;
import java.rmi.RemoteException;
import java.rmi.Remote;
public interface EchoFactory extends Remote
Echo getEcho(String userName) throws RemoteException;
////////////// EchoFactoryImpl.java
package emi.server;
import java.rmi.RemoteException;
import java.rmi.server.UnicastRemoteObject;
public class EchoFactoryImpl extends UnicastRemoteObject implements EchoFactory
EchoFactoryImpl() throws RemoteException {};
public Echo getEcho(String userName) throws RemoteException
EchoImpl echoRef = new EchoImpl(userName);
return (Echo)echoRef;
////////////// EchoImpl.java
package emi.server;
import java.rmi.RemoteException;
import java.rmi.server.UnicastRemoteObject;
import java.util.*;
public class EchoImpl extends UnicastRemoteObject implements Echo
private String userName;
public EchoImpl() throws RemoteException
public EchoImpl(String userName) throws RemoteException
this.userName = userName;
public Date getTime()
Etim e = new Etim();
e.setTimeAct();
return e.get();
////////////// EchoServer.java
package emi.server;
import java.rmi.Naming;
import java.rmi.RMISecurityManager;
public class EchoServer
public static void main(String args[]) throws Exception
// Create and install the security manager
System.setSecurityManager(new RMISecurityManager());
// Create the servant instance for registration
EchoFactory factoryRef = new EchoFactoryImpl();
// Bind the object to the rmiregistry
Naming.rebind("EchoFactory", factoryRef);
System.out.println("Echo object ready and bound to the name 'EchoFactory'!");
////////////// Etim.java
package emi.server;
import java.util.*;
import java.text.*;
// this is my central class working up all time problems .. many hundred lines of code
// I think, you must not look at this code ist setting and reading time
// this is only a subset of methods for this example
public class Etim
private Date dat;
private Calendar cal;
public Etim()
cal = Calendar.getInstance(); // Gregorianischer Kalender
dat = new Date(0L); // January 1, 1970, 00:00:00
cal.clear();
* Zeit lesen.
public Date get()
return dat;
// setting the time
public void setDate( Date d )
dat.setTime( d.getTime() );
cal.setTime(dat);
// gets my time-class to the current system-clock
public void setTimeAct()
long millis;
millis = System.currentTimeMillis();
setMilli(millis);
* Zeit setzen.
public void setMilli(long millis)
dat.setTime(millis);
cal.setTime(dat);
// time in german format: day.month.year hour:minute:second:millisecond
public String toString()
return toStringTagMoJahr() + " " + toStringStdMiSek() +
":" + cal.get(Calendar.MILLISECOND);
* Ausgabeformat Tag.Monat.Jahr (z.B. 01.01.2001).
public String toStringTagMoJahr()
SimpleDateFormat s = new SimpleDateFormat("dd.MM.yyyy");
return s.format(dat);
* Ausgabeformat Stunde:Minute:Sekunde (00:00:00 - 23:59:59).
public String toStringStdMiSek()
SimpleDateFormat s = new SimpleDateFormat("HH:mm:ss");
return s.format(dat);

Hello willy51,
Thank you for answering.
I think, your comment of the design is true - its a problem when starting up in a new enviroment and
you have nobody who shows you the right direction at the beginning. Talking personally together only
10 minutes is better than writing a noval.
I thing the following model of a client works better:
concept:
- visualize a personal time class continously evgery second
- if there is a connection to a server set the time-class with the server time
- if you loss connection, try to reconnect
question:
in which situation hangs connectToServer() ?
(whithout the simple errors : no rmiregistry, no rmi-server)
public class EchoClient
private String hostname;
public static void main(String args[]) throws Exception
// my internal TIME-Class
Etim acttim = new Etim();
// Create and install the security manager
System.setSecurityManager(new RMISecurityManager());
// remote call
Echo echoRef1 = null;
String url = new String("rmi://"+ servername:port +"/EchoFactory");
// displaying continous the time, technic = swing.timer
EchoClientDisplay disp = new EchoClientDisplay(acttim);
disp.StartTimer();
// transfering continous the time from the server, technic = swing.timer
// The state of transfer from server = offline
EchoClientTransfer trans = new EchoClientTransfer(acttim);
trans.StartTimer();
// Connect to server
connectToServer(url, echoRef1, trans);
// wait for ever, if connection failed, try every 5 seconds a reconnect to server
while(true)
// test, if connection failed. The connections fails if the Object EchoClientTransfer
// get a error, when it asks the server for the time ( remote call )
if(trans.getStatus() == false ) // test, if connection failed
connectToServer(url, echoRef1, trans);
// try it again after 5 seconds
Thread.sleep(5000);
private static void connectToServer(String url, Echo echoRef1, EchoClientTransfer trans)
System.out.println("Retry connection");
// Connect to server
while( true )
try
//get the remote factory object from the registry
EchoFactory remoteFactory = (EchoFactory)Naming.lookup(url);
//get references to new EchoImpl instances
echoRef1 = remoteFactory.getEcho("User Meyer");
// reactivate Datatransfer because I have now a new connection to the server
trans.reactivateAfterConnectionError(echoRef1);
// end of initialisation
break;
catch( Exception e )
//>>>>>>> Error initialising connection to server. try again after 5 seconds"
Thread.sleep(5000); // retry after 5 seconds

How to access local connection factory created within Foreign Server in OSB

Hi All
I am facing an issue in my config plan. We have a RIB Foreign server with the following local connection factory:
jms/RibAqJmsXATopicConnectionFactory
I am using the below in my configuration plan:
<cus:envValueAssignments>
<xt:envValueType>Service URI</xt:envValueType>
<xt:location xsi:nil="true"/>
<xt:owner>
<xt:type>ProxyService</xt:type>
<xt:path>RLTPReturnToWarehouse/ProxyServices/ConsumeRIBRTWMessages</xt:path>
</xt:owner>
<xt:value xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema">jms://localhost:7001/jms.RibAqJmsXATopicConnectionFactory/jms.etASNInFromRIBToWH1</xt:value>
</cus:envValueAssignments>
and i am getting the below error:
[java]
[java] Loading customization File ./dev/OSBCustomizationFile.xml
[java] Customization applied to the created resources only []
[java] com.bea.wli.config.customization.EnvValueCustomization@553c13
[java] Unexpected error: com.bea.wli.sb.transports.TransportException
[java] Problem invoking WLST - Traceback (innermost last):
[java] File "D:\VFUKScripts\DeploymentScripts\osb\import.py", line 200, in ?
[java] File "D:\VFUKScripts\DeploymentScripts\osb\import.py", line 122, in importToALSBDomain
[java] com.bea.wli.sb.transports.TransportException: Failed to lookup connection factory jms.RibAqJmsXATopicConnectionFactory
what am i missing here?

[java] com.bea.wli.sb.transports.TransportException: Failed to lookup connection factory jms.RibAqJmsXATopicConnectionFactory
Looks like the JNDI that you created for the ConnectionFactory is not reflected in the server.
Login to WLS Console> Summary of Servers > server_name > View JNDI Tree
Browse to the JNDI tree and see if your JNDI is visible there. If it is not then, please restart the server and recheck.
Once you are able to find it in the JNDI tree, then execute the customization file.
If you have modified the existing JNDI properties (that have a small exclamatory symbol) then any changes to those are not reflected till all the servers in the cluster are restarted.
If it still does not work, then recreate a new Connection with a different name and then retry. It should work then.
Thanks,
Patrick

10.1.3.4 - db Adapter connection factory has been stopped.

I created a process which had a custom sql operation to read data from a db table. It was working fine, but now I am getting a weird error
file:/apps/oracle/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_SiebelRMAShipmentIn_bpel_1.0_d9f7e6fe5e3f4daf12e5a856c48d4ff9.tmp/getShipmentRecords.wsdl [ getShipmentRecords_ptt::getShipmentRecords(getShipmentRecordsInput_msg,getShipmentRecordsOutputCollection) ] - WSIF JCA Execute of operation 'getShipmentRecords' failed due to: Pure SQL Exception. Pure SQL Execute of select a.row_id, a.asset_num, a.SERIAL_NUM, o.ORDER_NUM, oi.LN_NUM from s_asset a, s_order_item oi, s_order o where a.REF_NUMBER_2 = o.ORDER_NUM and oi.X_SHIP_ASSET_ID is null and oi.STATUS_CD <> 'Closed' and oi.ORDER_ID = o.row_id and a.X_ORDER_LN_NUM = oi.LN_NUM and a.ship_dt >= sysdate - 10 and a.X_ORDER_LN_NUM >= 1 failed. Caused by Exception [TOPLINK-4002] (Oracle TopLink - 10g Release 3 (10.1.3.4.0) (Build 080602)): oracle.toplink.exceptions.DatabaseException Internal Exception: java.sql.SQLException: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.Error Code: 0. [Caused by: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.] ; nested exception is: ORABPEL-11633 Pure SQL Exception. Pure SQL Execute of select a.row_id, a.asset_num, a.SERIAL_NUM, o.ORDER_NUM, oi.LN_NUM from s_asset a, s_order_item oi, s_order o where a.REF_NUMBER_2 = o.ORDER_NUM and oi.X_SHIP_ASSET_ID is null and oi.STATUS_CD <> 'Closed' and oi.ORDER_ID = o.row_id and a.X_ORDER_LN_NUM = oi.LN_NUM and a.ship_dt >= sysdate - 10 and a.X_ORDER_LN_NUM >= 1 failed. Caused by Exception [TOPLINK-4002] (Oracle TopLink - 10g Release 3 (10.1.3.4.0) (Build 080602)): oracle.toplink.exceptions.DatabaseException Internal Exception: java.sql.SQLException: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.Error Code: 0. [Caused by: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.] The Pure SQL option is for border use cases only and provides simple yet minimal functionality. Possibly try the "Perform an operation on a table" option instead. </summary>
<detail>Internal Exception: java.sql.SQLException: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.Error Code: 0</detail>
I don't get it, whats happening ? why does the adapter care what i am running inside a custom sql step. all it is supposed to do is execute the sql and return the values. Why is it forcing me to rewrite the operation which was working before ?

well as always...nothing works like restart of the server. Issue resolved.

FTP Adapter ORABPEL-11407 Connection closed error.

Hiiii friends
I have configured the connection factory for FTP Adapter (not defined any connection pool). My BPEL process poll the ftp location to get the file.
But no bpel instance is getting generated and domain.log shows the following error. Can you help me in this issue ?
+<2009-06-26 04:09:59,140> <INFO> <default.collaxa.cube.engine.deployment> Process "ReadEmp" (revision "1.0") successfully loaded.+
+<2009-06-26 04:10:10,666> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::init - Initializing the JCA activation age+
nt, processId='bpel://localhost/default/ReadEmp~1.0/
+<2009-06-26 04:10:10,667> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::initiateInboundJcaEndpoint - Creating and+
initializing inbound JCA endpoint for:
process='bpel://localhost/default/ReadEmp~1.0/'
+<2009-06-26 04:10:10,667> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::initiateInboundJcaEndpoint - Creating and+
initializing inbound JCA endpoint for:
process='bpel://localhost/default/ReadEmp~1.0/'
domain='default'
WSDL location='ReadEmpPL.wsdl'
portType='GetEmpOp_ptt'
operation='GetEmpOp'
+activation properties={portType=GetEmpOp_ptt}+
+<2009-06-26 04:10:10,678> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - endpointActivation for p+
ortType=GetEmpOp_ptt, operation=GetEmpOp
+<2009-06-26 04:10:10,763> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> ENDPOINT ACTIVATION CALLED IN FTP ADAPTER+
+<2009-06-26 04:10:10,765> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - successfully completed e+
ndpointActivation for portType=GetEmpOp_ptt, operation=GetEmpOp
+<2009-06-26 04:10:10,765> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Connection Created+
+<2009-06-26 04:10:40,516> <WARN> <default.collaxa.cube.activation> <File Adapter::Inbound> PollWork::run exiting, Worker thread will die+
+<2009-06-26 04:20:11,382> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Poller raising Alert for exception : ORABPEL-11407+
Connection closed error.
Connection closed for Host: corpdevapp10.
Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
+<2009-06-26 04:20:41,429> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Connection Created+
I am not sure what exactly is happening here. I have already established the successful connection with the same FTP server using different FTP clients.

sounds like the ftp server closed the connection. did you try to use other ftp clients from the same machine where the bpel engine is running?
Mark

Cannot bind tibco's jms connection factory to wls jndi

we are using wls 6.1 sp2. I am trying to bind tibco's jms connection factory
and queue from a standalone client to weblogic's jndi tree so that apps on wls
can lookup these object in wls jndi locally. I have included the required classes
in the classpath for both the client and wls. I am able to bind the queue successfully
and am able to use it successfully too, but I am not able to bind the tib's queue
or topic connection factory. I am getting the following errors. I checked and
double checked the classpath and
Start server side stack trace:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationExcep
tion
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
com.tibco.tibjms.n
aming.TibjmsFederatedTopicConnectionFactory; InstantiationException
Start server side stack trace:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
com.tibco.tibjms.naming.Ti
bjmsFederatedTopicConnectionFactory; InstantiationException
Start server side stack trace:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
anybody any ideas.
I am also trying to bind the tib's jndi tree in wls jndi tree through a reference
object and am passing a composite name for lookup. I am getting a cannotproceedexception.
I wonder if the weblogic jndi can be federated.
anybody any ideas or pointers
thanks
Devaraju, Sushant

Seems there is a bug in the tibco jms software.
thanks
Devaraju, Sushant
"sushant" <[email protected]> wrote:
>
we are using wls 6.1 sp2. I am trying to bind tibco's jms connection
factory
and queue from a standalone client to weblogic's jndi tree so that apps
on wls
can lookup these object in wls jndi locally. I have included the required
classes
in the classpath for both the client and wls. I am able to bind the queue
successfully
and am able to use it successfully too, but I am not able to bind the
tib's queue
or topic connection factory. I am getting the following errors. I checked
and
double checked the classpath and
Start server side stack trace:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception
is:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationExcep
tion
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
com.tibco.tibjms.n
aming.TibjmsFederatedTopicConnectionFactory; InstantiationException
Start server side stack trace:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
com.tibco.tibjms.naming.Ti
bjmsFederatedTopicConnectionFactory; InstantiationException
Start server side stack trace:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
anybody any ideas.
I am also trying to bind the tib's jndi tree in wls jndi tree through
a reference
object and am passing a composite name for lookup. I am getting a cannotproceedexception.
I wonder if the weblogic jndi can be federated.
anybody any ideas or pointers
thanks
Devaraju, Sushant

OJMS Connection Factory Error

Similar Messages

Maybe you are looking for