My Oracle Support Banner

"Address is already in use" Error When Using Multiple Connector Instances (Doc ID 2397762.1)

Last updated on MAY 18, 2018

Applies to:

Oracle Documaker - Version 12.6 and later
Information in this document applies to any platform.

Symptoms

On : 12.6 version, Enterprise Edition

Multiple Connector instances

Tried to create additional service to Run connector, but the new instance does not work. An error is thrown that Connection pool cannot be established and Address is already in use.
This approach is advised in Connector admin guide provided by Oracle but not able to achieve this functionality.

ERROR
-----------------------

java.net.BindException: Address already in use: JVM_Bind
at java.net.DualStackPlainSocketImpl.bind0(Native Method)
at java.net.DualStackPlainSocketImpl.socketBind(Unknown Source)
at java.net.AbstractPlainSocketImpl.bind(Unknown Source)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.bind(Unknown Source)
at java.net.ServerSocket.(Unknown Source)
at java.net.ServerSocket.(Unknown Source)
at oracle.documaker.ecmconnector.engine.CommandChannel.(CommandChannel.java:28)
at oracle.documaker.ecmconnector.engine.Engine.configure(Engine.java:263)
at oracle.documaker.ecmconnector.engine.Engine.initializeConnector(Engine.java:149)
at oracle.documaker.ecmconnector.engine.Engine.runService(Engine.java:48)
at oracle.documaker.ecmconnector.applications.Server.main(Server.java:24)
log4j:WARN No appenders could be found for logger (oracle.documaker.ecmconnector.engine.Engine).
log4j:WARN Please initialize the log4j system properly.
4)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedConstructorAccessor17.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at oracle.documaker.ecmconnector.connectorapi.frameworks.SourceFramework.initialize(SourceFramework.java:182)
... 4 more
Caused by: oracle.documaker.ecmconnector.connectorapi.exceptions.SourceException: DocumakerSource configuration failure - Cannot get a

connection, pool error Timeout waiting for idle object
at oracle.documaker.ecmconnector.documakersource.DocumakerSource.(DocumakerSource.java:168)
... 8 more
ecmconnector.documakersource.DocumakerSource.(DocumakerSource.java:168)
... 9 more
racle.documaker.ecmconnector.documakersource.DocumakerSource.(DocumakerSource.java:168)
... 9 more



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. create a second Documaker connector service instance, as per Running Multiple Services chapter in Documaker Connector Admin Guide.
2.start successfully first instance
3.trying to start the second instance: the error is raised


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!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.