JDK-8027429 : Add diagnostic command VM.info to get hs_err print-out
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2013-10-29
  • Updated: 2022-12-06
  • Resolved: 2015-11-14
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 b96Fixed
Related Reports
Relates :  
JDK-8054891 - Sustaining: more diagnostic commands
Sub Tasks
JDK-8296227 :  
Release Note: Jcmd vm.info backported to jdk8u-cpu - Resolved
Description
We print a lot of good information about the system when we print an hs_err file. We should create a diagnostic command VM.info to print the same information without crashing. This information can be used for example when filing a bug to provide basic information about the system

We should skip printing the THREAD information, as that is not interesting in this case. Also, of course, we shouldn't print the header with "A fatal error has been detected...". We still want the full Java version though.
Comments
URL: http://hg.openjdk.java.net/jdk9/jdk9/hotspot/rev/009f8ea8999c User: lana Date: 2015-12-10 00:26:59 +0000
10-12-2015
URL: http://hg.openjdk.java.net/jdk9/hs-rt/hotspot/rev/009f8ea8999c User: coleenp Date: 2015-11-14 17:24:17 +0000
14-11-2015
To be more clear I was suggesting that the new Dcmd utilize the existing sources of information rather than trying to piggy-back on the VMError report. If we enumerate what information we want to see then when can identify where that information is available.
30-10-2015
Some background: We have this command in JRockit. The information you gather when you crash to give a good summary of what system you run on is pretty much exactly the information you need to get a good summary on a system that has not crashed. The JRockit command is extremely useful for support, and saves a lot of work going back and forth asking about system information. Also, if we write something new in the hs_err file, like if there has been any out of memory errors, we often would want the same information in the VM.info output. From my experience in Sustaining/Support, I can't think of any information you would want in VM.info that you wouldn't also want in the hs_err file and the other way around, apart from details about the crash (obviously). I don't see a reason to exactly enumerate what information VM.info should provide. From a sustaining/support perspective, we want a one-stop command to gather as much useful information as possible, which is the same idea we have for the hs_err file.
29-10-2015
There already exist various sources of runtime information (system properties, monitoring/management APIs) that can provide this kind of information. We need to enumerate exactly what kind of information this Dcmd should provide, not just loosely refer to what the hs_err crash log provides.
29-10-2015
Is it planned to integrate this before Aug 14 2015 to meet the JEP 228 (which is blocked by this) integration date?
30-07-2015
Not strictly a hs_err improvement, rather a diagnostic command, removing hs_err improvement from subject.
30-04-2015
Talked to Mattis - at this time he expects sustaining to own this one. Thanks :-)
19-02-2014
This would be good to get in JDK7 and above
29-10-2013