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

Issue No: 3
Date: 29-July-2010
Version: weblogic portal 10.3.2
I created 2 WL 10.3 Domains. I can start the admin server in domain but when I start the second admin server i get the following error:
starting weblogic with Java version:
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_E
RROR_TRANSPORT_INIT(197)
Starting WLS with line:
C:\bea\JDK160~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket
,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -XX:Com
pileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -XX:MaxPermSize=160m
-Xverify:none -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:
javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.
sbconsole... -Dplatform.home=C:\bea\WLSERV~1.3 -Dwls.home=C:\bea\WLSERV~1.3\serv
er -Dweblogic.home=C:\bea\WLSERV~1.3\server -Dweblogic.management.discover=tru
e -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true
-Dweblogic.ext.dirs=C:\bea\patch_wlw1030\profiles\default\sysext_manifest_classp
ath;C:\bea\patch_wls1030\profiles\default\sysext_manifest_classpath;C:\bea\patch
_cie670\profiles\default\sysext_manifest_classpath;C:\bea\patch_alsb1031\profile
s\default\sysext_manifest_classpath -Dweblogic.Name=TestAdmin2 -Djava.security.p
olicy=C:\bea\WLSERV~1.3\server\lib\weblogic.policy weblogic.Server
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_E
RROR_TRANSPORT_INIT(197)
Stopping PointBase server...

Solution:

1) Changing the configuration in the setDomainEnv.cmd will resolve this issue. Check the DEBUG_PORT it might be the same for both the domains.

OR

2) Remove the following from the script that is used to start the server.
-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n.
This is used to debug the process and I don't think you may need to start a production system in debug mode. Lets try this.

OR

3) This issue you may face due to heap memory also. Tune the Memory arguments according to your RAM and then try it and try keeping maximum and minimum heap as same, may be your JVM is taking too much of time to manage heap; and also try out increasing you -XX:MaxPermSize accordingly,
check your garbage collection data, that will show you what the problem is, check for PermGeneration committed and Used size. If committed size is used completely try increasing MaxPermSize. Take a thread dump of your running process and analyze those by detecting deadlock and stuck threads.