How to fix “Address already in use: JVM_Bind” error?

This article answers following queries:

·         How to resolve if dispatcher or server node of the J2ee application server fails to start?

·         How to fix “Address already in use: JVM_Bind” error?

·         How to address “Address already in use: JVM_Bind” error in std_dispatcher.out or std_server0.out log?

·         What is the location of std_server0.out file?

·         What is the location of std_dispatcher.out file?

---------------------------------------------------------------------------

In SAP Netweaver 7.0 environment, sometimes, dispatcher or server0 node of the J2EE application server fails to start. Please check various logs under work directory.

std_server0 and std_dispatcher.out files will be under /usr/sap/<SID>/inst_name/work directory.

Mainly, If we notice “Address already in use: JVM_Bind” errors in these files, then the issue is with port number. That particular port is being used by another process thus preventing java node to start.

To resolve this issue, we need to

i)             Go through above mentioned logs and identify the port that is being blocked

ii)            Identify the process that is using the port and kill that process. Various network tools like netstat can be used to identify the problematic process

iii)           Kill the problematic process or restart the HOST to release that port

iv)           Once that problematic port is released, restart the J2EE system