Home/ Questions/Q 8578047
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T20:17:54+00:00

this functionality used to work and now it seems broken, I a do not

  • 0

this functionality used to work and now it seems broken, I a do not know how to diagnose it.
I am developing a java Applet that runs in a browser. I used to set up the runtime parameters in the java console to (Windows platform):

-Djava.compiler=NONE -Xnoagent -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=n,suspend=n

This setting appears both in the User and System tabs in the Java console.

Then I would start a debug session in eclipse for my applet project and set it to listen on port 8000. When I launch the browser and the applet is loaded, it would attach to eclipse and I was able to debug and set breakpoints, etc.

Now, it seems that this is no longer happening. When I launch the debug session in Eclipse, I do see port in LISTENING mode and owned by javaw.exe, which is correct. The only problem is that when the browser loads the Java plugin, it does not honor the “Runtime Parameters” and does not connect to the listening debug session in eclipse.

I have the latest Java update installed.

What else should I be looking into?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I just resolved my issue.
    I edited:
    C:\users\\AppData\LocalLow\Sun\Java\Deployment\deployment.properties
    and added the pararameters as follows:

    deployment.javaws.jre.0.args=-Djava.compiler\=NONE -Xnoagent -Xdebug -Xrunjdwp\:transport\=dt_socket,address\=8000,server\=n,suspend\=n

    When i added the runtime parameters through the UI, they went to
    “deployment.javaws.jre.1.args” so I duplicated them into “deployment.javaws.jre.0.args”

    • 0