JDK-8021585 : Setting trace level 5 in console does not enable all tracing.
  • Type: Bug
  • Component: deploy
  • Affected Version: 7u40
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2013-07-26
  • Updated: 2014-02-12
  • Resolved: 2013-07-30
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.
7u40 b36Fixed 8Fixed
in the console, hitting "5" is supposed to turn on all tracing, but only the first 7 trace levels are turned on.
We have added 3 additional TraceLevel values since this was implemented without updating the console code:
TraceLevel.UI, TraceLevel.PRELOADER, TraceLevel.RULESET.
none of these can be turned on from the console.
Verified using 7u40-b42

Verified it with 7u40 #43

Risk assessment from Andy: This is a very simple no risk fix. It is partially a DRS bug because the DRS implementation created a new TraceLevle, TraceLevel.RULESET. This level, along with the previous 2 added TraceLevels (UI and PRELOADER) , were never set when hitting "5" in Console (which otherwise sets all trace levels.) so DRS users who hit 5 in console were never seing DRS trace statements.

Reproduced with 7u40 nightly #40. Pre-verified with 7u40 nightly #43.

SQE-OK to get this issue fixed for 7u40

users having problems debugging DRS problems because hitting 5 in console does not enable TraceLevel.RULESET