Custom JSP Fails To Execute BPEL Process
Friday, January 29, 2010
When running a custom application with a jsp calling a bpel processs, got 500 Internal Server Error..
"ejb/collaxa/system/DomainManagerBean" bean; exception reported is:
"javax.naming.NameNotFoundException: ejb/collaxa/system/DomainManagerBean not found
at com.evermind[Oracle Application Server Containers for J2EE 10g
(10.1.2.0.2)].server.rmi.RMIContext.lookup(RMIContext.java:164)
at com.evermind[Oracle Application Server Containers for J2EE 10g
(10.1.2.0.2)].server.ApplicationContext.lookup(ApplicationContext.java:333)
at com.evermind[Oracle Application Server Containers for J2EE 10g
(10.1.2.0.2)].server.ApplicationContext.lookup(ApplicationContext.java:120)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.oracle.bpel.client.util.BeanRegistry.lookupDomainManagerBean(BeanRegistry.java:218)
at com.oracle.bpel.client.auth.DomainAuthFactory.authenticate(DomainAuthFactory.java:83)
at com.oracle.bpel.client.Locator.(Locator.java:140)
at com.oracle.bpel.client.taglibs.LocatorTag.doStartTag(LocatorTag.java:73)
at _Vacation__Request__Submit._jspService(Vacation_Request_Submit.jsp:2)
[/Vacation_Request_Submit.jsp]
Cause
Custom application does not have permission to access bpel engine because bpel engine is not specified as a parent application.
Solution
To implement the solution, please execute the following steps:
1. stop oc4j container.
2. In the sever.xml change from
<application name="your_application" path="../applications/your_application.ear" />
to <application name="your_application" path="../applications/your_application.ear" parent="orabpel" auto-start="true" />
3. save the file and run
dcmctl updateconfig -ct oc4j
4. delete the your_application folder under both
OC4J_BPEL/applications and
OC4J_BPEL/applications-deployments
5. Restart OC4J_BPEL container.
At this moment both folders should be recreated and this approach should resolve
"javax.naming.NameNotFoundException: ejb/collaxa/system/DomainManagerBean not found" error.