Excessive Active Directory connections

(Doc ID 837392.1)

Last updated on MAY 02, 2016

Applies to:

Oracle Business Process Management Suite - Version 6.0.4 to 6.0.4
Information in this document applies to any platform.
***Checked for relevance on 18-Feb-2013***

Symptoms

When BPM is configured as a hybrid environment using MS Active Directory. 

There is an excessive number of open connections to AD occurring periodically.

Engine logs show the following error:

<[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <Kernel>> <> <> <1241796174602> <BEA-101017>
<[weblogic.servlet.internal.WebAppServletContext@2c0bd5f - appName: '08-workspace-XAFDIDS',
name: 'workspace', context-path: '/workspace'] Root cause of ServletException.

java.lang.Error: Error starting thread: Not enough storage is available to process this command.

at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:574)
at com.sun.jndi.ldap.Connection.<init>(Connection.java:212)
at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1578)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2596)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:283)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
at fuego.directory.hybrid.ldap.JNDIQueryExecutor.doTheSearch(JNDIQueryExecutor.java:254)
at fuego.directory.hybrid.ldap.JNDIQueryExecutor.select(JNDIQueryExecutor.java:219)
at fuego.directory.hybrid.ldap.JNDIQueryExecutor.selectAllFromView(JNDIQueryExecutor.java:101)
at fuego.directory.hybrid.ldap.JNDIQueryExecutor.selectAllFromView(JNDIQueryExecutor.java:79)
at fuego.directory.hybrid.ldap.Repository.selectAllFromView(Repository.java:76)
at
fuego.directory.hybrid.ldap.LDAPOrganizationParticipantAccessor.fetchHumanParticipant(LDAPOrganizationParticipantAccessor.java:154)
at fuego.directory.hybrid.HybridParticipantAccessor.fetchHumanParticipant(HybridParticipantAccessor.java:178)
at sun.reflect.GeneratedMethodAccessor400.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:739)
at $Proxy52.fetchHumanParticipant(Unknown Source)
at fuego.directory.hybrid.ldap.LDAPOrganizationAuthenticationAccessor.authenticate(LDAPOrganizationAuthenticationAccessor.java:62)
at fuego.directory.hybrid.ldap.LDAPOrganizationAuthenticationAccessor.connect(LDAPOrganizationAuthenticationAccessor.java:90)
at fuego.directory.hybrid.HybridAuthenticationAccessor.connect(HybridAuthenticationAccessor.java:114)
at sun.reflect.GeneratedMethodAccessor399.invoke(Unknown Source)

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