< prev index next >

core/tests/org.openjdk.jmc.flightrecorder.rules.jdk.test/src/test/resources/baseline/JfrRuleBaseline.xml

Print this page 

        
@@ -159,10 +159,17 @@
 <score>0.0</score>
 <shortDescription>The program generated 0 exceptions per second during 1.017 s starting at 4/26/18 12:10:30 PM.</shortDescription>
 <longDescription>The program generated 0 exceptions per second during 1.017 s starting at 4/26/18 12:10:30 PM.</longDescription>
 </rule>
 <rule>
+<id>Fatal Errors</id>
+<severity>Not Applicable</severity>
+<score>-1.0</score>
+<shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
+<longDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.&lt;p&gt;They are either not available in this version of Java, or must be enabled in a third-party component. If you are using an older Java version, then you can consider upgrading.</longDescription>
+</rule>
+<rule>
 <id>FewSampledThreads</id>
 <severity>Information</severity>
 <score>29.510744962334375</score>
 <shortDescription>There are fewer sampled threads than the total number of hardware threads (cores).</shortDescription>
 <longDescription>There are fewer sampled threads than the total number of hardware threads (cores).&lt;p&gt;1 threads with at least 4 method samples were found, but the machine has 32 hardware threads (cores). The application might benefit from a higher level of parallelism. This could also be caused by threads doing something else than running Java code, for example running native code or spending time in the JVM internals.&lt;p&gt;This recording is only 9.903 s long, consider creating a recording longer than 20 s for improved rule accuracy.</longDescription>

@@ -547,10 +554,17 @@
 <score>0.0</score>
 <shortDescription>The program generated 0 exceptions per second during 1.210 s starting at 4/26/18 12:12:47 PM.</shortDescription>
 <longDescription>The program generated 0 exceptions per second during 1.210 s starting at 4/26/18 12:12:47 PM.</longDescription>
 </rule>
 <rule>
+<id>Fatal Errors</id>
+<severity>Not Applicable</severity>
+<score>-1.0</score>
+<shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
+<longDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.&lt;p&gt;They are either not available in this version of Java, or must be enabled in a third-party component. If you are using an older Java version, then you can consider upgrading.</longDescription>
+</rule>
+<rule>
 <id>FewSampledThreads</id>
 <severity>Information</severity>
 <score>29.510744962334375</score>
 <shortDescription>There are fewer sampled threads than the total number of hardware threads (cores).</shortDescription>
 <longDescription>There are fewer sampled threads than the total number of hardware threads (cores).&lt;p&gt;1 threads with at least 4 method samples were found, but the machine has 32 hardware threads (cores). The application might benefit from a higher level of parallelism. This could also be caused by threads doing something else than running Java code, for example running native code or spending time in the JVM internals.&lt;p&gt;This recording is only 9.921 s long, consider creating a recording longer than 20 s for improved rule accuracy.</longDescription>

@@ -935,10 +949,17 @@
 <score>-1.0</score>
 <shortDescription>This rule requires events to be available from the following event types: 'Exception Statistics'.</shortDescription>
 <longDescription>The Thrown Exceptions rule requires events to be available from the following event types: 'Exception Statistics'.&lt;p&gt;They were either disabled during the recording or there might not have happened anything to trigger an event. Event settings like period and threshold may also prevent some events from being emitted. If you are using JMC to create a flight recording, then you can enable and configure event types in the Start Flight Recording wizard. If you are starting the flight recording from the command line, then you can use the settings parameter of &lt;a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html"&gt;-XX:FlightRecorderOptions&lt;/a&gt;.</longDescription>
 </rule>
 <rule>
+<id>Fatal Errors</id>
+<severity>Not Applicable</severity>
+<score>-1.0</score>
+<shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
+<longDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.&lt;p&gt;They are either not available in this version of Java, or must be enabled in a third-party component. If you are using an older Java version, then you can consider upgrading.</longDescription>
+</rule>
+<rule>
 <id>FewSampledThreads</id>
 <severity>Not Applicable</severity>
 <score>-1.0</score>
 <shortDescription>This rule requires events to be available from the following event types: 'CPU Information', 'Method Profiling Sample', 'Recording Setting'.</shortDescription>
 <longDescription>The Parallel Threads rule requires events to be available from the following event types: 'CPU Information', 'Method Profiling Sample', 'Recording Setting'.&lt;p&gt;They were either disabled during the recording or there might not have happened anything to trigger an event. Event settings like period and threshold may also prevent some events from being emitted. If you are using JMC to create a flight recording, then you can enable and configure event types in the Start Flight Recording wizard. If you are starting the flight recording from the command line, then you can use the settings parameter of &lt;a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html"&gt;-XX:FlightRecorderOptions&lt;/a&gt;.</longDescription>

@@ -1323,10 +1344,17 @@
 <score>0.0</score>
 <shortDescription>The program generated 0 exceptions per second during 1.000 s starting at 4/25/18 11:38:36 AM.</shortDescription>
 <longDescription>The program generated 0 exceptions per second during 1.000 s starting at 4/25/18 11:38:36 AM.</longDescription>
 </rule>
 <rule>
+<id>Fatal Errors</id>
+<severity>Not Applicable</severity>
+<score>-1.0</score>
+<shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
+<longDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.&lt;p&gt;They are either not available in this version of Java, or must be enabled in a third-party component. If you are using an older Java version, then you can consider upgrading.</longDescription>
+</rule>
+<rule>
 <id>FewSampledThreads</id>
 <severity>Not Applicable</severity>
 <score>-1.0</score>
 <shortDescription>This rule requires events to be available from the following event types: 'CPU Information', 'Method Profiling Sample', 'Recording Setting'.</shortDescription>
 <longDescription>The Parallel Threads rule requires events to be available from the following event types: 'CPU Information', 'Method Profiling Sample', 'Recording Setting'.&lt;p&gt;They were either disabled during the recording or there might not have happened anything to trigger an event. Event settings like period and threshold may also prevent some events from being emitted. If you are using JMC to create a flight recording, then you can enable and configure event types in the Start Flight Recording wizard. If you are starting the flight recording from the command line, then you can use the settings parameter of &lt;a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html"&gt;-XX:FlightRecorderOptions&lt;/a&gt;.</longDescription>

@@ -1711,10 +1739,17 @@
 <score>0.0</score>
 <shortDescription>The program generated 0 exceptions per second during 999.487 ms starting at 4/4/14 11:17:06 AM.</shortDescription>
 <longDescription>The program generated 0 exceptions per second during 999.487 ms starting at 4/4/14 11:17:06 AM.</longDescription>
 </rule>
 <rule>
+<id>Fatal Errors</id>
+<severity>Not Applicable</severity>
+<score>-1.0</score>
+<shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
+<longDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.&lt;p&gt;They are either not available in this version of Java, or must be enabled in a third-party component. If you are using an older Java version, then you can consider upgrading.</longDescription>
+</rule>
+<rule>
 <id>FewSampledThreads</id>
 <severity>OK</severity>
 <score>0.0</score>
 <shortDescription>There were no problems with the amount of sampled threads.</shortDescription>
 <longDescription>There were no problems with the amount of sampled threads.&lt;p&gt;There are more sampled threads than the amount of hardware threads. This indicates that the application has enough parallelism for the available hardware.&lt;p&gt;This recording is only 5.171 s long, consider creating a recording longer than 20 s for improved rule accuracy.</longDescription>

@@ -2099,10 +2134,17 @@
 <score>0.0</score>
 <shortDescription>The program generated 0 exceptions per second during 1.009 s starting at 4/4/14 8:54:34 AM.</shortDescription>
 <longDescription>The program generated 0 exceptions per second during 1.009 s starting at 4/4/14 8:54:34 AM.</longDescription>
 </rule>
 <rule>
+<id>Fatal Errors</id>
+<severity>Not Applicable</severity>
+<score>-1.0</score>
+<shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
+<longDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.&lt;p&gt;They are either not available in this version of Java, or must be enabled in a third-party component. If you are using an older Java version, then you can consider upgrading.</longDescription>
+</rule>
+<rule>
 <id>FewSampledThreads</id>
 <severity>OK</severity>
 <score>0.0</score>
 <shortDescription>There were no problems with the amount of sampled threads.</shortDescription>
 <longDescription>There were no problems with the amount of sampled threads.&lt;p&gt;There are more sampled threads than the amount of hardware threads. This indicates that the application has enough parallelism for the available hardware.&lt;p&gt;This recording is only 5.136 s long, consider creating a recording longer than 20 s for improved rule accuracy.</longDescription>

@@ -2487,10 +2529,17 @@
 <score>0.0</score>
 <shortDescription>The program generated 0 exceptions per second during 1.054 s starting at 4/24/18 10:08:53 AM.</shortDescription>
 <longDescription>The program generated 0 exceptions per second during 1.054 s starting at 4/24/18 10:08:53 AM.</longDescription>
 </rule>
 <rule>
+<id>Fatal Errors</id>
+<severity>Not Applicable</severity>
+<score>-1.0</score>
+<shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
+<longDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.&lt;p&gt;They are either not available in this version of Java, or must be enabled in a third-party component. If you are using an older Java version, then you can consider upgrading.</longDescription>
+</rule>
+<rule>
 <id>FewSampledThreads</id>
 <severity>Information</severity>
 <score>29.510744962334375</score>
 <shortDescription>There are fewer sampled threads than the total number of hardware threads (cores).</shortDescription>
 <longDescription>There are fewer sampled threads than the total number of hardware threads (cores).&lt;p&gt;1 threads with at least 4 method samples were found, but the machine has 32 hardware threads (cores). The application might benefit from a higher level of parallelism. This could also be caused by threads doing something else than running Java code, for example running native code or spending time in the JVM internals.&lt;p&gt;This recording is only 4.902 s long, consider creating a recording longer than 20 s for improved rule accuracy.</longDescription>

@@ -2875,10 +2924,17 @@
 <score>2.573808918421875</score>
 <shortDescription>The program generated 515 exceptions per second during 28.060 s starting at 9/24/15 10:08:58 AM.</shortDescription>
 <longDescription>The program generated 515 exceptions per second during 28.060 s starting at 9/24/15 10:08:58 AM.</longDescription>
 </rule>
 <rule>
+<id>Fatal Errors</id>
+<severity>Not Applicable</severity>
+<score>-1.0</score>
+<shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
+<longDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.&lt;p&gt;They are either not available in this version of Java, or must be enabled in a third-party component. If you are using an older Java version, then you can consider upgrading.</longDescription>
+</rule>
+<rule>
 <id>FewSampledThreads</id>
 <severity>OK</severity>
 <score>0.0</score>
 <shortDescription>There were no problems with the amount of sampled threads.</shortDescription>
 <longDescription>There were no problems with the amount of sampled threads.&lt;p&gt;There are more sampled threads than the amount of hardware threads. This indicates that the application has enough parallelism for the available hardware.</longDescription>

@@ -3265,10 +3321,17 @@
 <score>-1.0</score>
 <shortDescription>This rule requires events to be available from the following event types: 'Exception Statistics'.</shortDescription>
 <longDescription>The Thrown Exceptions rule requires events to be available from the following event types: 'Exception Statistics'.&lt;p&gt;They were either disabled during the recording or there might not have happened anything to trigger an event. Event settings like period and threshold may also prevent some events from being emitted. If you are using JMC to create a flight recording, then you can enable and configure event types in the Start Flight Recording wizard. If you are starting the flight recording from the command line, then you can use the settings parameter of &lt;a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html"&gt;-XX:FlightRecorderOptions&lt;/a&gt;.</longDescription>
 </rule>
 <rule>
+<id>Fatal Errors</id>
+<severity>Not Applicable</severity>
+<score>-1.0</score>
+<shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
+<longDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.&lt;p&gt;They are either not available in this version of Java, or must be enabled in a third-party component. If you are using an older Java version, then you can consider upgrading.</longDescription>
+</rule>
+<rule>
 <id>FewSampledThreads</id>
 <severity>Not Applicable</severity>
 <score>-1.0</score>
 <shortDescription>This rule requires events to be available from the following event types: 'CPU Information', 'Method Profiling Sample', 'Recording Setting'.</shortDescription>
 <longDescription>The Parallel Threads rule requires events to be available from the following event types: 'CPU Information', 'Method Profiling Sample', 'Recording Setting'.&lt;p&gt;They were either disabled during the recording or there might not have happened anything to trigger an event. Event settings like period and threshold may also prevent some events from being emitted. If you are using JMC to create a flight recording, then you can enable and configure event types in the Start Flight Recording wizard. If you are starting the flight recording from the command line, then you can use the settings parameter of &lt;a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html"&gt;-XX:FlightRecorderOptions&lt;/a&gt;.</longDescription>



< prev index next >