My Quotes

When U were born , you cried and the world rejoiced
Live U'r life in such a way that when you go

Wednesday, December 23, 2009

JBoss Port Binding Error

1.   Cause of Error

JBoss comes with many socket based services that open listening ports

This might be due to the reason that JBoss is having conflict with some of the ports with other applications and thus causing JBoss not to start properly.

2.   Log file to look into


3.   Log message to look into

<<Latest Time Stamp>> WARN  [ServiceController] Problem starting service jboss:service=Naming
java.rmi.server.ExportException: Port already in use: 1098; nested exception is: Address already in use
        at sun.rmi.transport.tcp.TCPTransport.listen(
        at sun.rmi.transport.tcp.TCPTransport.exportObject(
        at sun.rmi.transport.tcp.TCPEndpoint.exportObject(
        at sun.rmi.transport.LiveRef.exportObject(

The above port number highlighted in bold is just a sample. This can be potentially any port number which could cause Jboss not to startup properly.

4.   List of port that could potentially cause the problem

The suggested list of ports of JBoss which could cause the BindException is
the typical ports JBoss uses. A range of 1098-8093 certainly covers the default port usage for jboss


Additional ports found in the all configuration:

5.   Sample port configuration changes

The following sections illustrate the customer support representative with the frequent port number which might cause the conflict and their suggested file path.
This also enables the support personnel to identify the exact match XMl tags they need to look in from the document which is of ease.

In all these cases stop the JBoss service as given in step 6. Do the changes and then re-start the service.


File Name                              

Tag Block to look for

  • Port for JNP
<!-- The listening port for the bootstrap JNP service. Set this to -1
        to run the NamingService without the JNP invoker listening port.
            <attribute name="Port">1100</attribute>
This requires a change in the application too. Please escalate to the first level escalation.

  • Port for RMI
<!-- The port of the RMI naming service, 0 == anonymous -->
      <attribute name="RmiPort">1097</attribute>
Change the port 1097 by 11097


File Name


Tag Block to look for

      <!-- A HTTP/1.1 Connector on port 351 -->
            <Connector port="351" address="${jboss.bind.address}"
      This requires a change in the application too. Please escalate to the first level

No comments :