OS: Windows XP SP 2
I can successfully get debugging of .jsp files to work under Tomcat locally,
but I think I am missing something in my understanding of how it should work
When I debug my middleware code I build it and copy the .class files onto
the remote machine and start a debug session using the remote tab. I startup
the JVM and Tomcat on the remote machine with the following settings.
-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005
This means to me that the JVM has started and Tomcat has initialized but the
JVM is listening on port 5005 for a remote connection attempt from a
When I want to debug .jsp code locally I pick Tomcat local settings on the
debug tab and start debugging. It uses the following settings to startup
-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=mylocalmachine:1652,suspend=y,server=n
Intellij runs Tomcat via the batch files. I understand this to say that the
JVM starts up but does not initialize Tomcat yet and then waits to attach to
Intellij on port 1652. Tomcat then intializes after a successful debugger
When I want to debug remote .jsp code I copy the .jsp files onto the remote
server, pick the Tomcat/remote settings under the debugger and this is the
settings it suggests.
-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=mylocalmachine:1862,suspend=y,server=n
Now I do not understand this. When I start Tomcat with these settings, it
just exits. I assume that since server=n it exits when it does not find a
I am confused how this is supposed to work.