JDK-8158565 : Consider to clean up classresolve "info" level msgs
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2016-06-02
  • Updated: 2016-08-11
  • Resolved: 2016-07-27
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 9
9 b131Fixed
Related Reports
Duplicate :  
JDK-8158567 - Consider to clean up classresolve "info" level msgs
Relates :  
JDK-8146551 - The output from -Xlog:classresolve=info looks not useful
Description
In some of the info level classresolve msgs it shows  (super) or (interface) etc which seems helpful to any user. But the ones showing only the source line number don't seem to have any meaning. In running with info level, millions of source line number lines are printed and they are not really that helpful to understand what is going on. Could those by moved to debug or trace level if they are useful for JVM debugging?


[68.987s][info ][classresolve] java.util.IdentityHashMap$KeyIterator java.util.IdentityHashMap$IdentityHashMapIterator (super)
[68.987s][info ][classresolve] java.util.IdentityHashMap$KeySet java.util.IdentityHashMap$KeyIterator IdentityHashMap.java:976
[68.987s][info ][classresolve] java.util.IdentityHashMap$KeySet java.util.IdentityHashMap$KeyIterator IdentityHashMap.java:976
Comments
OK I see the logging is largely modified some time after b111, I just tried the tip of jdk9 and see "class,resolve" is now in debug level. You can close this as a dup or whatever as you see fit.
08-06-2016
All of the class+resolve logging statements were already moved to the debug level - see JDK-8146551. Arguably the line-number versions could/should move to trace.
08-06-2016
I was using b111 when I filed this, since I was moving forward thru the versions to see where my app broke with Jigsaw. If this logging is fixed in a later version, I will try b121 later today and see how it looks.
08-06-2016
There is one info level message in closed code, meaning 8146551 was incomplete. (I would consider this to be a bug and not an enhancement since it is unintended behavior resulting from an error in a previous change.) I am wondering what build and what test you were using to produce this output.
08-06-2016
The "classresolve" tag no longer exists. What build are you using?
07-06-2016