4.0.1 hang when debug enabled

[schwarcz]

When I enable debugging and launch JBoss 4.0.1 (Windows XP Pro SP2 & JDSK 5.0), there is no cpu activity and no logging output once the message "Listening for transport dt_socket at address: 8787" is echoed.

I'm assuming it is some sort of config problem at my end but wonder if anybody has any suggestions?


C:\jboss-4.0.1\bin>echo CLASSPATH: C:\Program Files\Java\jdk1.5.0\lib\tools.jar;C:\jboss-4.0.1\bin\\run.jar
CLASSPATH: C:\Program Files\Java\jdk1.5.0\lib\tools.jar;C:\jboss-4.0.1\bin\\run.jar

C:\jboss-4.0.1\bin>echo .
.

C:\jboss-4.0.1\bin>echo ===============================================================================
===============================================================================

C:\jboss-4.0.1\bin>echo .
.

C:\jboss-4.0.1\bin>"C:\Program Files\Java\jdk1.5.0\bin\java" -classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:t
ransport=dt_socket,address=8787,server=y,suspend=y -Dprogram.name=debug.bat -Xms128m -Xmx512m "-Djava.endorsed.dirs=C:\
jboss-4.0.1\bin\\..\lib\endorsed" -classpath "C:\Program Files\Java\jdk1.5.0\lib\tools.jar;C:\jboss-4.0.1\bin\\run.jar"
org.jboss.Main
Warning: classic VM not supported; client VM will be used
Listening for transport dt_socket at address: 8787
^CTerminate batch job (Y/N)? y

[schwarcz]

Well, I still can't figure it out but I have narrowed down the issues some.

No problem running JBoss 3.6 in debugging mode.

Identical problem running either JBoss 4.0.0 or JBoss 4.0.1

Falling back to the 1.4 JDK doesn't help.

Still hoping for some insight from you JBoss experts out there.

[starksm64]

This is standard behavior for the jpda configuration when you include the suspend=y option. The vm is waiting for a debugger to attach to the process. Read the jpda options and behavior:
http://java.sun.com/j2se/1.5.0/docs/guide/jpda/conninv.html

[schwarcz]

Thanks so much.