Symptom
- You notice the outboundRA has failed to start and remains in red status;
- Even if you try to restart application "com.sap.aii.adapter.idoc.sapjra.outboundRA" it still won't come up;
- From the default traces you can see error similar to below:
Global [startApp] operation of application [sap.com/com.sap.aii.adapter.idoc.sapjra.outboundRA] finished with errors for [381] ms on server process [22337650] [
>>> Errors <<<
1). com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "XX".
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:433)
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:130)
at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:366)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:509)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:403)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:332)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:560)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocal(ParallelAdapter.java:335)
at com.sap.engine.services.deploy.server.DeployServiceImpl.execute(DeployServiceImpl.java:1950)
at com.sap.engine.services.deploy.server.remote.RemoteCommandFactory$StartRemoteCommand.execute(RemoteCommandFactory.java:804)
at com.sap.engine.services.deploy.server.remote.RemoteCommandFactory$RemoteCommand$1.run(RemoteCommandFactory.java:142)
at com.sap.engine.services.deploy.server.remote.RemoteCommandFactory$RemoteCommand$1.run(RemoteCommandFactory.java:137)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at com.sap.engine.services.deploy.server.remote.RemoteCommandFactory$RemoteCommand.executeInSubjectDoAs(RemoteCommandFactory.java:137)
at com.sap.engine.services.deploy.server.remote.RemoteCaller$1.run(RemoteCaller.java:592)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: javax.naming.NameAlreadyBoundException: Object with name "XX" is already bound.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:450)
at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:944)
at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:797)
at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:1023)
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:528)
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:415)
... 19 more
Read more...
Environment
- SAP NetWeaver 7.5
- SAP Process Integration
- SAP Process Orchestration
Product
SAP NetWeaver all versions ; SAP Process Integration all versions
Keywords
connection factory lookup error, outboundRA, clonedRA, connection factory duplicate name, Cannot bind, Object with name, already bound , KBA , BC-XI-CON-IDO , Idoc Adapter J2EE , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview