BPEL 11g: LDAP Failover Set in Security Provider Configuration is not Working (Doc ID 1545149.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle SOA Suite - Version 11.1.1.5.0 and later
Information in this document applies to any platform.

Symptoms

LDAP failover set in security provider configuration is not working. Two LDAP servers are configured for a security provider to provide failover capabilities in the event the primary server becomes unavailable. When the primary server is unavailable, a human task component in a BPM process fails whilst accessing the failed server. The request should automatically failover to the secondary LDAP server but this does not occur.

The following errors occur:

Servlet failed with Exception
javax.el.ELException: ORABPEL-30010

Error in creating reply message for Web Services.
Error in creating reply message for Web Services.
The Web Service input could be invalid causing this exception. Check the Web Service input for correctness. The input could also be validated against XML schema definition that describes the operation input. It being valid, this is a system error.
at com.sun.el.parser.AstValue.invoke(Unknown Source)
...
Caused By: ORABPEL-30010

Error in creating reply message for Web Services.
...
Caused By: ORABPEL-30504
Internal error in Verification Service.
Internal error in Verification Service for user myuser. lookupUser.
...
Caused By: ORABPEL-10516
Cannot find user.
An error occurred while getting user "myuser" from configuration "jazn.com"
Check if the user exists in the repository specified by the configurations. Contact Oracle Support Services if error is not fixable.
at oracle.tip.pc.services.identity.jps.JpsProvider.lookupUser(JpsProvider.java:855)
at oracle.tip.pc.services.identity.jps.AuthorizationServiceImpl.lookupUser(AuthorizationServiceImpl.java:230)
...
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: oracle.security.idm.OperationFailureException: javax.naming.CommunicationException: xxx.xx.xx.13:389 [Root exception is java.net.ConnectException: Connection refused]
at oracle.security.idm.providers.stdldap.JNDIPool.acquireConnection(JNDIPool.java:82)
at oracle.security.idm.providers.stdldap.LDIdentityStoreFactory.acquireConnection(LDIdentityStoreFactory.java:750)
...
Caused By: javax.naming.CommunicationException: xxx.xx.xx.13:389 [Root exception is java.net.ConnectException: Connection refused]
at com.sun.jndi.ldap.Connection.(Connection.java:208)
...
Caused By: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)

 

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