ESB Service Calling BPEL Process Using Java Binding Throws NamingException (Doc ID 754378.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle ESB - Version: 10.1.3.3 to 10.1.3.4 - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.
***Checked for relevance on 31-Oct-2010***

Symptoms

You have a ESB service calling BPEL process through Java binding.
BPEL is associated with OID for authentication.
So when the ESB calls BPEL authentication/authorization fails throwing following error
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode xmlns="">env:ESBMessageProcessingFailed</faultcode>
<faultstring xmlns="">Failed to create "ejb/collaxa/system/DeliveryBean" bean; exception
reported is: "javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException:
Not authorized; nested exception is:
javax.naming.AuthenticationException: Not authorized [Root exception is
javax.naming.AuthenticationException: Not authorized]
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:69)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.oracle.bpel.client.util.BeanRegistry.lookupDeliveryBean(BeanRegistry.java:279)
at com.oracle.bpel.client.delivery.DeliveryService.getDeliveryBean(DeliveryService.java:299)
at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.java:194)
at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.java:178)
at oracle.tip.esb.server.service.impl.bpel.BPELService.processBusinessEvent(BPELService.java:353)
at
oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatch
er.java:407)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:165)
at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
.....
Caused by: javax.naming.AuthenticationException: Not authorized
at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:100)
at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:69)
at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:700)
at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:244)
at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:228)
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:302)
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:56)
... 39 more
</faultstring>
</env:Fault></env:Body></env:Envelope>

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms