JDK-8015681 : Control panel doesn't allow you to set parameters for JVM that actually runs
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 7u21
  • Priority: P2
  • Status: Resolved
  • Resolution: Duplicate
  • Submitted: 2013-05-06
  • Updated: 2014-11-17
  • Resolved: 2013-07-11
Related Reports
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Description
FULL PRODUCT VERSION :
java version  " 1.7.0_21 " 
Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
Java HotSpot(TM) Client VM (build 23.21-b01, mixed mode, sharing)

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 6.1.7601]

A DESCRIPTION OF THE PROBLEM :
I'm trying to debug an applet running in the browser plugin. In previous versions, I could start the Java control panel and add parameters on the Java page. I can still do that, but the parameters are set for the javaw.exe run-time. I can see in Process Explorer that java.exe is what's actually running in the browser. I tried to add java.exe as a run-time in the Java dialog, but JVMs added on the User tab in this dialog are now never saved.

So I can change the parameters for javaw.exe successfully, but these parameters are not passed onto java.exe. I can't configure java.exe separately. When my applet launches in the browser, I am unable to connect to the applet with my debugger.

REGRESSION.  Last worked in version 7u17

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Open the Java Control Panel, go to the Java tab, and click View...
2. Click in the Runtime Parameters column for the 32-bit JVM.
3. Enter the debug parameters, e.g. -agentlib:jdwp=transport=dt_socket,address=8888,server=y,suspend=y.
4. Click OK and then Apply. Click View... again to verify that the parameters were saved. Note that the path to the JVM is to javaw.exe.
5. Start debug environment, e.g. IntelliJ.
6. Go to applet-hosting application and launch applet.
7. Try to connect to applet with debugger. This will fail.
8. Inspect the running plugin with Process Explorer. This will show that the plugin JVM is java.exe.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The JVM would be the same in the control panel as what is actually running in the browser. Once the applet is running, I should be able to connect with my debugger.
ACTUAL -
The JVM is not the same in the control panel as what is actually running in the browser. Once the applet is running, I cannot connect with my debugger.

REPRODUCIBILITY :
This bug can be reproduced always.
Comments
dup of 8016005
11-07-2013

This issue is fully duplicates the set of cases described by "JDK-8016005 Remote debugging for applets in a browser is no longer working" and " JDK-8013735 can't start JWS in debug with jdk1.7.0_21 installed" JDK-8016005 covers applet case JDK-8013735 covers web start case. As soon as both these issues are resolved this issue is resolved also.
03-07-2013

Changed priority to P2 since duplicates have P2 priority
24-06-2013

The are two cases here: applets and JWS. For JWS it duplicates JDK-8013735 "can't start JWS in debug with jdk1.7.0_21 installed" For applets it duplicates JDK-8016154 and JDK-8016005 "Remote debugging for applets in a browser is no longer working"
18-06-2013

duplicate of your bug ? please check.
31-05-2013