Loading ...Fix Weblogic/NodeManager ERROR: transport error 202: bind failed: Address already in use
During Oracle SOA, AIA or other Fusion Middleware components installation, you might run into the following errors during startup:
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:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
/app/oracle/middleware/user_projects/domains/SOA_domain/bin/startWebLogic.sh: line 179: 15926 Aborted ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}Here is a quick fix for it
milly 11:13 am on July 20, 2011
The root cause was due to two managed servers using the same debugging port.
In this case, you can edit the setDomainEnv.sh file and turn debugging off.
Searching for debugFlag=”true” near line 145 of the default setDomainEnv.sh and change it to false.
debugFlag="false"