You are currently reviewing an older revision of this page.
When starting JBoss, the following error is printed in application server log:
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service [...]: JBAS017112: Address already in use: bind / [IP]:[Port] ... Caused by: java.net.BindException: Address already in use: bind
JBoss then fails to deploy.
This error message is returned when the service printed in the error message can't be started. This means that the port defined in standalone.xml located in <JBOSS_HOME>/standalone/configuration is already being used.
<JBOSS_HOME>/standalone/configuration
Make sure that the port defined for the problematic service is free. To identify the problematic service, locate the service name or port and compare it to the service name or port defined in standalone.xml.
Examples:
The following error message refers to one of the management services defined in standalone.xml and using port 9999:
management
MSC000001: Failed to start service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jboss.remoting.server.management: JBAS017112: Address already in use: bind 127.0.0.1:9999
The following error message refers to the remoting service defined in standalone.xml and using port 4447:
remoting
MSC00001: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017112: Address already in use: bind /127.0.0.1:4447
Note: If it is not possible to liberate the default port, it is possible to manually modify the desired port by changing the value for the service in standalone.xml.
This article applies to all versions of Appian using JBoss as an application server.
Last Reviewed: February 2017