private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
If you have a web application deployed into Jetty you can interact with it remotely from a debugging perspective easily. The basics are that you must start up the remote JVM with additional parameters and then start up a remote debugging session in Eclipse for the webapp in question. This is easily accomplished.
This example assumes you are deploying your web application into the jetty-distribution.
Assuming you have your webapp deployed into jetty, there are two different ways to approach this:
Add the required parameters on the commandline like so.
$ java -Xdebug -agentlib:jdwp=transport=dt_socket,address=9999,server=y,suspend=n -jar start.jar
This approach is best used if you want to debug a particular jetty-distribution and not have to remember the commandline incantations.
and uncomment the --exec line, this is required if you are adding jvm options to the
start.ini file as jetty-start must generate the classpath required and fork a new
Add the parameters mentioned above in the Command Line option so your start.ini looks like this:
Uncomment any other jvm environmental options you so desire for your debugging session.
Regardless of the option chosen, you should see the following lines at the top of your jetty-distribution startup.