My Oracle Support Banner

BPM Workspace Throws "Root exception is java.net.BindException: Address already in use: connect" While Trying To Login (Doc ID 1365645.1)

Last updated on AUGUST 06, 2018

Applies to:

Oracle Business Process Management Suite - Version 10.3.1 and later
Information in this document applies to any platform.

Symptoms

BPM Directory Service has been configured as hybrid and connects to a single MSAD LDAP server.

MSAD LDAP server has been configured with primary and secondary / backup domains.

When users try to login into BPM Workspace or when users that are already logged in perform Workspace operations the following error message is shown:

Exception [javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: host_name.com:389 [Root exception is java.net.BindException: Address already in use: connect]]].


At some point, it's possible that the Workspace application won't start at all.

Workspace logs could show the following stack trace:

[<S> 0927 16:52:03.288] Main (<3> Fuego PAPI News Listener [bpmengine] Service [host_name/2009-07-07 15:09:22-04:00:17073807:22548098]): Exception [javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: host_name.com:389 [Root exception is java.net.BindException: Address already in use: connect]]].
[ (cont) ] Main: Caused by: javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: host_name.com:389 [Root exception is java.net.BindException: Address already in use: connect]]
[ (cont) ] Main: Caused by: host_name.com:389
[ (cont) ] Main: Caused by: Address already in use: connect
[ (cont) ] Main: fuego.directory.DirectoryRuntimeException: Exception [javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: host_name.com:389 [Root exception is java.net.BindException: Address already in use: connect]]].
[ (cont) ] Main: at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:85)
[ (cont) ] Main: at fuego.directory.hybrid.ldap.JNDIQueryExecutor.select(JNDIQueryExecutor.java:241)
[ (cont) ] Main: at fuego.directory.hybrid.ldap.JNDIQueryExecutor.selectAllFromView(JNDIQueryExecutor.java:105)
[ (cont) ] Main: at fuego.directory.hybrid.ldap.JNDIQueryExecutor.selectAllFromView(JNDIQueryExecutor.java:85)
[ (cont) ] Main: at fuego.directory.hybrid.ldap.Repository.selectAllFromView(Repository.java:54)
[ (cont) ] Main: at fuego.directory.hybrid.ldap.LDAPPollingEventGenerator.search(LDAPPollingEventGenerator.java:114)
[ (cont) ] Main: at fuego.directory.hybrid.ldap.LDAPPollingEventGenerator.buildCurrentProxies(LDAPPollingEventGenerator.java:108)
[ (cont) ] Main: at fuego.directory.provider.notifiers.BasePollingEventGenerator.generateEvents(BasePollingEventGenerator.java:51)
[ (cont) ] Main: at fuego.directory.hybrid.HybridMultipleEventGenerator.generateEvents(HybridMultipleEventGenerator.java:43)
[ (cont) ] Main: at fuego.directory.provider.notifiers.DirectoryNotifier.notifyChanges(DirectoryNotifier.java:403)
[ (cont) ] Main: at fuego.papi.impl.EngineNewsListener.processEngineNews(EngineNewsListener.java:286)
[ (cont) ] Main: at fuego.papi.impl.EngineAccess.processEngineNews(EngineAccess.java:173)
[ (cont) ] Main: at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.access$300(J2EEEngineAccessImpl.java:68)
[ (cont) ] Main: at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.onMessage(J2EEEngineAccessImpl.java:548)
[ (cont) ] Main: at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.dispatchMessages(J2EEEngineAccessImpl.java:744)
[ (cont) ] Main: at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.run(J2EEEngineAccessImpl.java:595)
[ (cont) ] Main: Caused by: javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: host_name.com:389 [Root exception is java.net.BindException: Address already in use: connect]]
[ (cont) ] Main: at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImpl(LdapNamingEnumeration.java:224)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreReferrals(LdapNamingEnumeration.java:362)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImpl(LdapNamingEnumeration.java:208)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreReferrals(LdapNamingEnumeration.java:362)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImpl(LdapNamingEnumeration.java:208)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapNamingEnumeration.hasMore(LdapNamingEnumeration.java:171)
[ (cont) ] Main: at fuego.directory.hybrid.ldap.JNDIQueryExecutor.doTheSearch(JNDIQueryExecutor.java:294)
[ (cont) ] Main: at fuego.directory.hybrid.ldap.JNDIQueryExecutor.select(JNDIQueryExecutor.java:215)
[ (cont) ] Main: ... 14 more
[ (cont) ] Main: Caused by: javax.naming.CommunicationException: host_name.com:389 [Root exception is java.net.BindException: Address already in use: connect]
[ (cont) ] Main: at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapReferralContext.java:74)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapReferralException.getReferralContext(LdapReferralException.java:132)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreReferrals(LdapNamingEnumeration.java:339)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImpl(LdapNamingEnumeration.java:208)
[ (cont) ] Main: ... 21 more
[ (cont) ] Main: Caused by: java.net.BindException: Address already in use: connect
[ (cont) ] Main: at java.net.PlainSocketImpl.socketConnect(Native Method)
[ (cont) ] Main: at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
[ (cont) ] Main: at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
[ (cont) ] Main: at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
[ (cont) ] Main: at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
[ (cont) ] Main: at java.net.Socket.connect(Socket.java:519)
[ (cont) ] Main: at java.net.Socket.connect(Socket.java:469)
[ (cont) ] Main: at java.net.Socket.<init>(Socket.java:366)
[ (cont) ] Main: at java.net.Socket.<init>(Socket.java:180)
[ (cont) ] Main: at com.sun.jndi.ldap.Connection.createSocket(Connection.java:349)
[ (cont) ] Main: at com.sun.jndi.ldap.Connection.<init>(Connection.java:184)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2616)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:287)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:134)
[ (cont) ] Main: at com.sun.jndi.url.ldap.ldapURLContextFactory.getObjectInstance(ldapURLContextFactory.java:35)
[ (cont) ] Main: at javax.naming.spi.NamingManager.getURLObject(NamingManager.java:584)
[ (cont) ] Main: at javax.naming.spi.NamingManager.processURL(NamingManager.java:364)
[ (cont) ] Main: at javax.naming.spi.NamingManager.processURLAddrs(NamingManager.java:344)
[ (cont) ] Main: at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:316)
[ (cont) ] Main: at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapReferralContext.java:93)
[ (cont) ] Main: ... 24 more

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
Cause
Solution


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.