Managed Server ERROR: transport error 202: bind failed: Address already in use

ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]

This Error Appeared when trying to start Managed server the Log Shown the above error, which already clear, in my case i have 2 managed server SOA and OSB in the same AdminServer each of them trying to access on the same PID process using Node Manager to solve this issue please follow the below steps.
Solutions :-
  • Inside Domain Path for example /u01/app/fmw/domains/Base_domain/bin
  • Edit setDomainEnv.sh and search for the below :-

if [ “${DEBUG_PORT}” = “” ] ; then
        DEBUG_PORT=”8453″
        export DEBUG_PORT
fi

if [ “${SERVER_NAME}” = “” ] ; then
        SERVER_NAME=”AdminServer”
        export SERVER_NAME
fi

  •  Add New Lines under the above to contain server name and available DEBUG_PORT on the server like the below:-

if [ “${SERVER_NAME}” = “soa_server1” ] ; then
   DEBUG_PORT=”7453″
   export DEBUG_PORT
fi

if [ “${SERVER_NAME}” = “osb_server1” ] ; then
   DEBUG_PORT=”7454″
   export DEBUG_PORT
fi

 Now Restart AdminServer and Try to start Managed Server, Take Backup from setDomainEvn.sh before editing.

Thank you
Osama mustafa

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.