KB-1099 Application server either fails to start with "Address already in use: bind / [IP]:[Port]" error thrown or 503 service unavailable error encountered

Parmida Borhani — Thu, 14 Nov 2019 00:38:08 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 11/14/2019 12:38:08 AM

Symptoms

When starting the application server, the application server either fails to start up, or if it does start, an HTTP 503 status code is encountered when attempting to access the login page:

The following error is also printed in application server log:

Caused by: java.net.BindException: Address already in use: bind

Cause

This error message is returned when the service printed in the error message can't be started. This means that the port defined in the error message is already being used. Ports can be defined in the following files:

Tomcat

server.xml located in <APPIAN_HOME>/tomcat/apache-tomcat/conf

JBoss

standalone.xml located in <JBOSS_HOME>/standalone/configuration

Action

Make sure that the port defined for the problematic service is free. To identify if there is a running process on that port, and identify that process's PID:

Linux

Run the following command: netstat -pnltu | grep -i "<PORT>"

If there is a running process on the port, you can kill the process with the following command: kill -9 <PID>

Windows

Open an Administrator Command Prompt and run the following command: netstat -a -b -o | findstr "<PORT>"
Open Task Manager, navigate to the "Performance" tab, and at the bottom click "Open Resource Monitor." From here, you can view listening ports and their respective PIDs.

If there is a running process on the port, you can kill the process with the following command: taskkill /F /PID <PID>

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 or server.xml for JBoss and Tomcat respectively.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2019

Tags: port, Tomcat, 503, application server, infrastructure, jboss

KB-1099 "JBAS017112: Address already in use: bind / [IP]:[Port]" error thrown during JBoss startup

Parmida Borhani — Thu, 14 Nov 2019 00:36:11 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 11/14/2019 12:36:11 AM

Symptoms

When starting the application server, the application server either fails to start up, or if it does start, an HTTP 503 status code is encountered when attempting to access the login page:

Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.

The following error is also printed in application server log:

Caused by: java.net.BindException: Address already in use: bind

Cause

Tomcat

server.xml located in <APPIAN_HOME>/tomcat/apache-tomcat/conf

JBoss

standalone.xml located in <JBOSS_HOME>/standalone/configuration

Action

Make sure that the port defined for the problematic service is free. To identify if there is a running process on that port, and identify that process's PID:

Linux

Run the following command: netstat -pnltu | grep -i "<PORT>"

If there is a running process on the port, you can kill the process with the following command: kill -9 <PID>

Windows

Open an Administrator Command Prompt and run the following command: netstat -a -b -o | findstr "<PORT>"
Open Task Manager, navigate to the "Performance" tab, and at the bottom click "Open Resource Monitor." From here, you can view listening ports and their respective PIDs.

If there is a running process on the port, you can kill the process with the following command: taskkill /F /PID <PID>

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2019

Tags: port, Tomcat, 503, application server, infrastructure, jboss

KB-1099 "JBAS017112: Address already in use: bind / [IP]:[Port]" error thrown during JBoss startup

Parmida Borhani — Wed, 13 Nov 2019 02:55:25 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2019 2:55:25 AM

Symptoms

When starting the application server, the application server either fails to start up, or if it does start, an HTTP 503 status code is encountered when attempting to access the login page:

Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

The following error is also printed in application server log:

Caused by: java.net.BindException: Address already in use: bind

Cause

Tomcat

server.xml located in <APPIAN_HOME>/tomcat/apache-tomcat/conf

JBoss

standalone.xml located in <JBOSS_HOME>/standalone/configuration

Action

Make sure that the port defined for the problematic service is free. To identify if there is a running process on that port, and identify that process's PID:

Linux

Run the following command: netstat -pnltu | grep -i "<PORT>"

If there is a running process on the port, you can kill the process with the following command: kill -9 <PID>

Windows

Open an Administrator Command Prompt and run the following command: netstat -a -b -o | findstr "<PORT>"
Open Task Manager, navigate to the "Performance" tab, and at the bottom click "Open Resource Monitor." From here, you can view listening ports and their respective PIDs.

If there is a running process on the port, you can kill the process with the following command: taskkill /F /PID <PID>

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2019

Tags: port, Tomcat, 503, application server, infrastructure, jboss

KB-1099 "JBAS017112: Address already in use: bind / [IP]:[Port]" error thrown during JBoss startup

Parmida Borhani — Wed, 13 Nov 2019 02:53:32 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2019 2:53:32 AM

Symptoms

When starting the application server, the application server either fails to start up, or if it does start, an HTTP 503 status code is encountered when attempting to access the login page:

Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.

The following error is also printed in application server log:

Caused by: java.net.BindException: Address already in use: bind

Cause

Tomcat

server.xml located in <APPIAN_HOME>/tomcat/apache-tomcat/conf

JBoss

standalone.xml located in <JBOSS_HOME>/standalone/configuration

Action

Make sure that the port defined for the problematic service is free. To identify if there is a running process on that port, and identify that process's PID:

Linux

Run the following command: netstat -pnltu | grep -i "<PORT>"

If there is a running process on the port, you can kill the process with the following command: kill -9 <PID>

Windows

Open an Administrator Command Prompt and run the following command: netstat -a -b -o | findstr "<PORT>"
Open Task Manager, navigate to the "Performance" tab, and at the bottom click "Open Resource Monitor." From here, you can view listening ports and their respective PIDs.

If there is a running process on the port, you can kill the process with the following command: taskkill /F /PID <PID>

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2019

Tags: application server, infrastructure, jboss

KB-1099 "JBAS017112: Address already in use: bind / [IP]:[Port]" error thrown during JBoss startup

Parmida Borhani — Wed, 13 Nov 2019 02:51:04 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2019 2:51:04 AM

Symptoms

When starting the application server, the application server either fails to start up, or if it does start, an HTTP 503 status code is encountered when attempting to access the login page:

Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.

The following error is also printed in application server log:

Caused by: java.net.BindException: Address already in use: bind

Cause

Tomcat

server.xml located in <APPIAN_HOME>/tomcat/apache-tomcat/conf

JBoss

standalone.xml located in <JBOSS_HOME>/standalone/configuration

Action

Make sure that the port defined for the problematic service is free. To identify if there is a running process on that port, and identify that process's PID:

Linux

Run the following command: netstat -pnltu | grep -i "<PORT>"

If there is a running process on the port, you can kill the process with the following command: kill -9 <PID>

Windows

Open an Administrator Command Prompt and run the following command: netstat -a -b -o | findstr "<PORT>"
Open Task Manager, navigate to the "Performance" tab, and at the bottom click "Open Resource Monitor." From here, you can view listening ports and their respective PIDs.

If there is a running process on the port, you can kill the process with the following command: taskkill /F /PID <PID>

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2019

Tags: application server, infrastructure, jboss

KB-1099 "JBAS017112: Address already in use: bind / [IP]:[Port]" error thrown during JBoss startup

Parmida Borhani — Wed, 13 Nov 2019 02:45:40 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2019 2:45:40 AM

Symptoms

When starting the application server, the application server either fails to start up, or if it does start, an HTTP 503 status code is encountered when attempting to access the login page:

Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.

The following error is also printed in application server log:

Caused by: java.net.BindException: Address already in use: bind

Cause

Tomcat: server.xml located in <APPIAN_HOME>/tomcat/apache-tomcat/conf

JBoss: standalone.xml located in <JBOSS_HOME>/standalone/configuration

Action

Make sure that the port defined for the problematic service is free. To identify if there is a running process on that port, and identify that process's PID:

Linux

Run the following command: netstat -pnltu | grep -i "<PORT>"

Windows

Open an Administrator Command Prompt and run the following command: netstat -a -b -o | findstr "<PORT>"
Open Task Manager, navigate to the "Performance" tab, and at the bottom click "Open Resource Monitor." From here, you can view listening ports and their respective PIDs.

If there is a running process on the port, you can kill the process with the below commands:

Linux

kill -9 <PID>

Windows

taskkill /F /PID <PID>

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2019

Tags: application server, infrastructure, jboss

KB-1099 "JBAS017112: Address already in use: bind / [IP]:[Port]" error thrown during JBoss startup

Parmida Borhani — Mon, 30 Jul 2018 03:56:23 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 3:56:23 AM

Symptoms

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.

Cause

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.

Action

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:

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:

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.

Affected Versions

This article applies to all versions of Appian using JBoss as an application server.

Last Reviewed: February 2017

Tags: application server, infrastructure, jboss

KB-1099 "JBAS017112: Address already in use: bind / [IP]:[Port]" error thrown during JBoss startup

Nick Vigilante — Wed, 22 Feb 2017 22:07:21 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/22/2017 10:07:21 PM

Symptoms

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.

Cause

Action

Examples:

The following error message refers to one of the management services defined in standalone.xml and using port 9999:

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:

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.

Affected Versions

This article applies to all versions of Appian using JBoss as an application server.

Last Reviewed: February 2017

Tags: application server, jboss