SOA 11g: Creation of Adapter JNDIs Causes Adapter to go to Prepared Status: <BEA-190125> <Internal Error occurred, Assertion Failed: No Initial Context for Jndi: javax.naming.CannotProceedException
(Doc ID 1285891.1)
Last updated on OCTOBER 15, 2019
Applies to:
Oracle SOA Suite - Version 11.1.1.3.0 and laterInformation in this document applies to any platform.
***Checked for relevance on 02-June-2014***
Symptoms
You have created SOA adapter JNDI resources from the WebLogic Console Deployments screen. You have created some JNDI names that are on the whole unique, but some parts may use the same text, for example:
eis/db/oltp/nonBatch
eis/as/fln/nonXA/nonBatch
These may create fine, but on restarting the Admin or SOA managed servers you get an error similar to the following in the managed server logfile $MIDDLEWARE_HOME/user_projects/domains/<your domain>/servers/<server name>/<server name>.out:
ADF Library non-OC4J post-deployment (millis): 12
<Jan 17, 2011 6:49:13 PM MST> <Error> <Connector> <BEA-190125> <Internal Error occurred, Assertion Failed: No Initial Context for Jndi: javax.naming.CannotProceedException; remaining name 'nonXA'
java.lang.AssertionError: Internal Error occurred, Assertion Failed: No Initial Context for Jndi: javax.naming.CannotProceedException; remaining name 'nonXA'
at weblogic.connector.common.Debug.throwAssertionError(Debug.java:2241)
at weblogic.connector.deploy.JNDIHandler.isJndiNameBound(JNDIHandler.java:938)
at weblogic.connector.deploy.JNDIHandler.bindConnectionFactory(JNDIHandler.java:168)
at weblogic.connector.outbound.RAOutboundManager.activatePool(RAOutboundManager.java:1076)
at weblogic.connector.outbound.RAOutboundManager.activate(RAOutboundManager.java:183)
Truncated. see log file for complete stacktrace
Caused By: javax.naming.CannotProceedException; remaining name 'nonXA'
at javax.naming.spi.ContinuationContext.getTargetContext(ContinuationContext.java:43)
at javax.naming.spi.NamingManager.getContinuationContext(NamingManager.java:770)
at weblogic.jndi.internal.BasicNamingNode.getContinuationCtx(BasicNamingNode.java:1180)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:216)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
Truncated. see log file for complete stacktrace
>
<Jan 17, 2011 6:49:13 PM MST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'DbAdapter'.
weblogic.application.ModuleException: weblogic.connector.exception.RAOutboundException:
There are 1 nested errors:
weblogic.management.DeploymentException: Bind operation failed: eis/db/oltp/nonXA, java.lang.AssertionError: Internal Error occurred, Assertion Failed: No Initial Context for Jndi: javax.naming.CannotProceedException; remaining name 'nonXA'
at weblogic.connector.deploy.JNDIHandler.bindConnectionFactory(JNDIHandler.java:219)
at weblogic.connector.outbound.RAOutboundManager.activatePool(RAOutboundManager.java:1076)
at weblogic.connector.outbound.RAOutboundManager.activate(RAOutboundManager.java:183)
at weblogic.connector.common.RAInstanceManager.activate(RAInstanceManager.java:433)
at weblogic.connector.deploy.ConnectorModule.activate(ConnectorModule.java:302)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:532)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:158)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1269)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
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:52)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:31)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:170)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:124)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
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: javax.naming.CannotProceedException; remaining name 'nonXA'
at javax.naming.spi.ContinuationContext.getTargetContext(ContinuationContext.java:43)
at javax.naming.spi.NamingManager.getContinuationContext(NamingManager.java:770)
at weblogic.jndi.internal.BasicNamingNode.getContinuationCtx(BasicNamingNode.java:1180)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:216)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
at weblogic.connector.deploy.JNDIHandler.isJndiNameBound(JNDIHandler.java:931)
at weblogic.connector.deploy.JNDIHandler.bindConnectionFactory(JNDIHandler.java:168)
at weblogic.connector.outbound.RAOutboundManager.activatePool(RAOutboundManager.java:1076)
at weblogic.connector.outbound.RAOutboundManager.activate(RAOutboundManager.java:183)
at weblogic.connector.common.RAInstanceManager.activate(RAInstanceManager.java:433)
at weblogic.connector.deploy.ConnectorModule.activate(ConnectorModule.java:302)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
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.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
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)
... 3 more
at weblogic.connector.deploy.ConnectorModule.activate(ConnectorModule.java:308)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:532)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
Truncated. see log file for complete stacktrace
Caused By: javax.naming.CannotProceedException; remaining name 'nonXA'
at javax.naming.spi.ContinuationContext.getTargetContext(ContinuationContext.java:43)
at javax.naming.spi.NamingManager.getContinuationContext(NamingManager.java:770)
at weblogic.jndi.internal.BasicNamingNode.getContinuationCtx(BasicNamingNode.java:1180)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:216)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
Truncated. see log file for complete stacktrace
This will also make the adapter deployment status go to a Prepared state instead of an Active state.
Changes
Possible upgrade from an OC4J 10g installation of SOA Suite to 11g, reusing adapter JNDI names that were used in the older OC4J installation.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |