My Oracle Support Banner

BpelIntegration Fails to Connect to SOA/BPEL Cluster and Throws "Failed to create "ejb/collaxa/system/DomainManagerBean" " (Doc ID 979983.1)

Last updated on MAY 16, 2023

Applies to:

Oracle WebCenter Content - Version 10.0 and later
Information in this document applies to any platform.

Symptoms

UCM BPEL integration is not working correctly. The BPEL server process and Content Server process are both up and running, but they are not communicating correctly and the following exception is thrown by SOA/BPEL into the UCM BpelIntegration's server log:

Event generated by user 'sysadmin' at host '10.0.0.11'. The Provider URL could not be found. com.oracle.bpel.client.ServerException: Failed to create "<DOMAIN>DomainManagerBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/DomainManagerBean not found
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:52)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.oracle.bpel.client.util.BeanRegistry.lookupDomainManagerBean(BeanRegistry.java:218)
at com.oracle.bpel.client.auth.DomainAuthFactory.validate(DomainAuthFactory.java:139)
at bpelintegration.OracleIntegration.loginDomain(OracleIntegration.java:131)
at bpelintegration.OraBpelHandler.loginDomain(OraBpelHandler.java:209)
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:585)
at intradoc.common.IdcMethodHolder.invokeMethod(ClassHelperUtils.java:466)
at intradoc.common.ClassHelperUtils.executeMethodReportStatus(ClassHelperUtils.java:142)
at intradoc.server.ServiceHandler.executeAction(ServiceHandler.java:77)
at intradoc.server.Service.doCodeEx(Service.java:490)
at intradoc.server.Service.doCode(Service.java:472)
at intradoc.server.ServiceRequestImplementor.doAction(ServiceRequestImplementor.java:1353)
at intradoc.server.Service.doAction(Service.java:452)
at intradoc.server.ServiceRequestImplementor.doActions(ServiceRequestImplementor.java:1194)
at intradoc.server.Service.doActions(Service.java:447)
at intradoc.server.ServiceRequestImplementor.executeActions(ServiceRequestImplementor.java:1114)
at intradoc.server.Service.executeActions(Service.java:433)
at intradoc.server.ServiceRequestImplementor.doRequest(ServiceRequestImplementor.java:635)
at intradoc.server.Service.doRequest(Service.java:1707)
at intradoc.server.ServiceManager.processCommand(ServiceManager.java:359)
at intradoc.server.IdcServerThread.run(IdcServerThread.java:197)

Caused by java.lang.Exception: Failed to create "ejb/collaxa/system/DomainManagerBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/DomainManagerBean not found
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:52)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.oracle.bpel.client.util.BeanRegistry.lookupDomainManagerBean(BeanRegistry.java:218)
at com.oracle.bpel.client.auth.DomainAuthFactory.validate(DomainAuthFactory.java:139)
at bpelintegration.OracleIntegration.loginDomain(OracleIntegration.java:131)
at bpelintegration.OraBpelHandler.loginDomain(OraBpelHandler.java:209)
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:585)
at intradoc.common.IdcMethodHolder.invokeMethod(ClassHelperUtils.java:466)
at intradoc.common.ClassHelperUtils.executeMethodReportStatus(ClassHelperUtils.java:142)
at intradoc.server.ServiceHandler.executeAction(ServiceHandler.java:77)
at intradoc.server.Service.doCodeEx(Service.java:490)
at intradoc.server.Service.doCode(Service.java:472)
at intradoc.server.ServiceRequestImplementor.doAction(ServiceRequestImplementor.java:1353)
at intradoc.server.Service.doAction(Service.java:452)
at intradoc.server.ServiceRequestImplementor.doActions(ServiceRequestImplementor.java:1194)
at intradoc.server.Service.doActions(Service.java:447)
at intradoc.server.ServiceRequestImplementor.executeActions(ServiceRequestImplementor.java:1114)
at intradoc.server.Service.executeActions(Service.java:433)
at intradoc.server.ServiceRequestImplementor.doRequest(ServiceRequestImplementor.java:635)
at intradoc.server.Service.doRequest(Service.java:1707)
at intradoc.server.ServiceManager.processCommand(ServiceManager.java:359)
at intradoc.server.IdcServerThread.run(IdcServerThread.java:197)

Changes

 

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
 To resolve potential issue #1:
 To resolve potential issue #2:
 To resolve potential issue #3:
 Note for all potential issues:
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.