JBoss failed to start rarely due to "Address already in use" caused by port conflict in same JBoss Java proccess

Solution Verified - Updated -

Issue

The following exception occurred when a JBoss server starts:

ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=org.jboss.ejb3.RemotingConnector state=Create
java.io.IOException: SocketServerInvoker[xxx.xxx.xxx.xxx:3873] error creating ServerSocket[xxx.xxx.xxx.xxx:3873]: Address already in use
    at org.jboss.remoting.transport.socket.SocketServerInvoker.createServerSockets(SocketServerInvoker.java:370)
    at org.jboss.remoting.transport.socket.SocketServerInvoker.start(SocketServerInvoker.java:250)
    at org.jboss.remoting.transport.Connector.start(Connector.java:344)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:616)
    at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
    at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)

I checked which process grabbed the port by using lsof or netstat commands, then same JBoss process listened 3873 port.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 5.x
    • 4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content