JDK-8013735 : can't start JWS in debug with jdk1.7.0_21 installed
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 7u21
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2013-04-23
  • Updated: 2014-11-17
  • Resolved: 2013-07-06
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7 JDK 8
7u40 b33Fixed 8Fixed
Related Reports
Duplicate :  
JDK-8015681 - Control panel doesn't allow you to set parameters for JVM that actually runs
Relates :  
JDK-8019497 - There is no the message "-Xmx256m" in the java console
Description
FULL PRODUCT VERSION :
1.7.0_21

ADDITIONAL OS VERSION INFORMATION :
Windows 7 Ultimate 64-bit (Ver=6.1.7601)

A DESCRIPTION OF THE PROBLEM :
Having 1.7.0_21 installed prevents you from debugging jnlp?s.

We have two versions of our product, which uses JWS and fat clients: one that uses 1.6 (jnlp specifies 1.6*) and one that uses 1.7.

After installing 1.7.0_21, the clients will not start if JWS debug is turned on.
Even when running the 1.6 jnlp, if you just have 1.7.0_21 installed, you can?t start a jnlp with debug turned on.  You don?t get any error messages, it just won?t start.  No manner of clearing the cache etc. fixes it.   Uninstalling 1.7.0_21 and reverting to 1.7.0.17 (the prior release) fixes the issue (Or just uninstalling 1.7.0.21, for the 1.6 applet)


REGRESSION.  Last worked in version 7u17

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
see notes in description

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
see notes in description
ACTUAL -
see notes in description

ERROR MESSAGES/STACK TRACES THAT OCCUR :
no error messages or other output

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
None found - had to revert to prior jdk release
Comments
justification: serious regression since 7u21. developer cannot debug webstart app with debugger.
03-07-2013
SQE-OK to get the issue fixed for 7u40.
03-07-2013
THE FIX: The fix ensures that VM parameters specified in Java Control Panel are always passes to JWS app . Please note that it doesn't fix problem with JAVAWS_VM_ARGS environment variable. Insecure VM arguments (including debug ones) specified in JAVAWS_VM_ARGS environment variable are still filtered out. But user could now debug JWS apps using VM arguments he specifies in JCP. The fix consists of two changes: 1) Fire relaunch if selected JRE has VM arguments specified in Java Control Panel. (The same changes in JREMatcher as for JDK-8016005 "Remote debugging for applets in a browser is no longer working" ). 2) Ensure that VM arguments specified in JCP are added to launch command.
18-06-2013
Preliminary patch from Daniil: src\common\share\native\secureArgs.c _T("-XX:+CMSIncrementalMode"), /* Enables the incremental mode */ + _T("-agentlib:"), /* Enables the debugging */ };
31-05-2013
Not reproducible on WinXp, reproducible on Win7.
31-05-2013
This needs more information from the submitter as Dmitry is not able to reproduce.
15-05-2013
this issue isn't reproducible to me - need more info from the submitter. it would be great if the submitter can provide more details. could you please confirm that the problem is specific to debug mode? please unset the JAVAWS_VM_ARGS env var and try to reproduce it again - is it still reproducible? if this is specific to debug mode, then it's strange, I don't remember that anything has been changed in deploy (7u21) at this point. I can't reproduce it in my environment - if I set the env variable and start my app (only 7u21 installed), then I can attach the debugger to the app. could you please also try running your app with tracing mode enabled see http://docs.oracle.com/javase/1.5.0/docs/guide/javaws/developersguide/troubleshooting.03.06.html the section - "Tracing and getting additional trace output" after running the app, log file should be created under $deployment.user.home/log does the log contain any exception? could you please attach the log to this bug report. also, could you please try a simple webstart app, for example, a demo from http://docs.oracle.com/javase/tutorial/deployment/webstart/deploying.html is it still reproducible?
07-05-2013
Update from user: 1) Name of the applet and link to the applet: It is our own software. We are a manufacturing software ISV, using RMI to communicate between the fat java client that gets loaded via JWS and the server side of the application. So it is our RMI fat client that won���t start. 2) Exact steps to reproduce this behavior: I have installed and uninstalled all possible combinations of JDK1.6.0_45 and JDK1.7.0_21, together and separately, and have verified that regardless of 64-bit/32-bit installation combinations, 1.7.0_21 is still the problem. (Note that debugging our client is something I do every day, so I���m not having issues actually getting debugging to work in general ��� it is just broken when I install 1.7.0_21.) a) My system is Windows 7 64-bit b) Attempting to start jnlp client with debugging on, so I can debug the client via Eclipse. To turn on debug, setting environment variable JAVAWS_VM_ARGS= -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5508 c) WITH any prior version of JDK 1.7.0 (e.g. 1.7.0_17), it all works fine d) WITHOUT 1.7.0_21 of any sort, and with only 1.6.0_45 installed (or any prior 1.6.0 release), it works fine, both with 32- and 64-bit versions of JDK e) As soon as I install either the 32- or 64-bit versions of JDK 1.7.0_21, it is impossible to start the client when the debug environment variable is set. This is true even though the jnlp specifies java version 1.6* There is a brief flash of the Java 7 logo, but even the java console (I always have logging turned on in the java control panel applet) does not appear. So there are no error messages, nothing gets logged to a console ��� it just flashes the logo and then nothing. f) As soon as I uninstall all versions of 1.7.0_21, the applet does start fine with the debug environment variable. g) I can re-install any old version of 1.7.0, like 1.7.0_17, and also starts fine
01-05-2013
I have requested the user to provide detailed information about the name and URL to the applet, clarification on what the user mean by "running JWS with debug on", hat's the exact command line to reproduce the bug, exact steps to reproduce the issue, screenshot and trace stack. Awaiting user response.
01-05-2013
can you provide more information on what you mean by running JWS with debug on ? what's the exact command line to reproduce the bug ?
25-04-2013