JDK-6850604 : System and deployment properties truncated in 6u14
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u10,6u14
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_xp,windows_vista
  • CPU: x86
  • Submitted: 2009-06-12
  • Updated: 2011-02-16
  • Resolved: 2009-08-19
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 6 JDK 7
6u18 b01Fixed 7Fixed
Related Reports
Relates :  
Description
FULL PRODUCT VERSION :
java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)

ADDITIONAL OS VERSION INFORMATION :
Windows Vista Business x64 Service Pack 2

A DESCRIPTION OF THE PROBLEM :
  From the Java Console, you can press "s" to "dump system and deployment properties". However, this is longer of any good use in 6u14, since this output is cut off in the middle like this:

deployment.version = 6.0
java.quick.star
Trace message truncated for length over 10K

Dumping the full system and deployment properties is a very convenient way of troubleshooting misc. things, but due to this change, it's hard to use this feature for anything now, since there doesn't seem to be any way to get the full list anymore.


STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Open any web page with an applet. Open the Java Console. Press "s" in the console, and you will see the truncated output.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
In 6u13 and earlier, pressing "s" in the console would give you the full list of system and deployment properties. This no happens in 6u14.
ACTUAL -
See "description" for details

REPRODUCIBILITY :
This bug can be reproduced always.

Release Regression From : 6u13
The above release value was the last known release where this 
bug was not reproducible. Since then there has been a regression.
webrev: http://sa.sfbay.sun.com/projects/deployment_data/6u17/6850604.0
testcase: http://web-east.east/www/tests/1.6.0_17/6850604/
risk: low
reviewers: Andy.Herrick, Hao.Dong, Jitender.Singh

Comments
EVALUATION I can't seem to reproduce this with JDK6u16. Maybe the above mentioned bugfix is in 14 and not yet in 16?
02-07-2009

EVALUATION This is caused by the fix to 6742564, where putting huge garbage into the console would hang VM (in the case of 6742564, it was trying to display a jnlp file that was actually a jar, huge pile of unprintable content). The simple fix there was just to limit the size to about 10K, but this causes this regression. We need to distinguish, in TraceMessage.java the differance between a legimitly huge string (such as the list of all System and deployment properties) and a lengthy mess of unprintable characters (such a jar file referenced as a jnlp file)
12-06-2009