« SQLPLus on Linux – get UP, DOWN, LEFT, RIGHT and other keys working
Searching in previously typed commands in linux command line »

Remote debugging Java Webstart application

  1. Download the xzy.jnlp file.
  2. Set the JAVAWS_VM_ARGS environment variable to
    -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8200 if the application runs with JDK 1.5 or lower
  3. From a console or cmd start the application with javaws xzy.jnlp or start with javaws -J”-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8200″ xyz.jnlp if you are using jdk 1.6
  4. Check that port 8200 is listening with netstat -an
    Netstat output
  5. Check your firewall settings.
  6. Define a new “Remote Java Applcation’ in Eclipse
  7. Set the IP and port.
  8. Start debugging.

(Source: Java forum & Trouble shooting and debugging guide)

Blogged with Flock

Explore posts in the same categories: Howto

This entry was posted on July 26, 2007 at 9:23 am and is filed under Howto. You can subscribe via RSS 2.0 feed to this post's comments. You can comment below, or link to this permanent URL from your own site.

4 Comments on “Remote debugging Java Webstart application”

  1. kumar Says:

    August 7, 2007 at 1:04 am

    Thanks for posting. I followed the steps as mentioned for JWS Remote Debugging but still i get exception.

    “Failed to connect to Remote VM. connection refused”. What could be possible reason ? I am using Eclipse, JDK1.6.0_02. I made sure Port and IP is entered correctly

  2. Joe Says:

    August 7, 2007 at 7:26 am

    Hi kumar!

    I realized that the theme of the blog cuts a part of the most important line of the post in some browsers… The longest line in the environment variable is: -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8200
    If you set it correctly and the problem still exists you should recheck that the debug port is opening after you start the webstart application on the client machine. (I added a screenshot to the post.) After that, try to connect from the “debugging” computer to the client machine with a simply telnet. If you are able to connect with telnet than we can be sure that there is no problem with the network connections and firewalls.
    Hope it helps.

    Joe

  3. fharper1961 Says:

    October 4, 2007 at 2:03 pm

    Hi Joe,

    I found that starting JWS from a shortcut icon worked just fine for debugging, once JAVAWS_VM_ARGS was set. For met it wasn’t necessary to explicitly start from cmd or a console.

    Frank

  4. Joe Says:

    October 4, 2007 at 8:00 pm

    Hi Frank,

    Thank you for your comment. (I almost forgot about this blog 🙂 )
    Your method is also fine but not in all cases. The troubleshooting guide (link is below the post) has the following note: “So when debugging, it is always best to download the jnlp file, and then launch javaws using that file as the arg.” (2.0) Special tip for all debugging.)
    In my case starting with the shortcut was not good. (SUN JDK 1.5_04)

    Joe


Leave a comment