United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-8021585 : Setting trace level 5 in console does not enable all tracing.

Details
Type:
Bug
Submit Date:
2013-07-26
Status:
Closed
Updated Date:
2013-09-09
Project Name:
JDK
Resolved Date:
2013-07-30
Component:
deploy
OS:
Sub-Component:
Empty
CPU:
Priority:
P3
Resolution:
Fixed
Affected Versions:
7u40
Fixed Versions:
7u40 (b36)

Related Reports
Backport:
Backport:
Backport:
Backport:

Sub Tasks

Description
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.
                                    

Comments
users having problems debugging DRS problems because hitting 5 in console does not enable TraceLevel.RULESET
                                     
2013-07-26
SQE-OK to get this issue fixed for 7u40
                                     
2013-07-27
Reproduced with 7u40 nightly #40. Pre-verified with 7u40 nightly #43.
                                     
2013-07-29
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.

                                     
2013-07-29
Verified it with 7u40 #43
                                     
2013-07-30
Verified using 7u40-b42
                                     
2013-09-09



Hardware and Software, Engineered to Work Together