< prev index next >

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

Print this page




 144 <severity>OK</severity>
 145 <score>0.0</score>
 146 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
 147 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
 148 </rule>
 149 <rule>
 150 <id>Errors</id>
 151 <severity>Not Applicable</severity>
 152 <score>-1.0</score>
 153 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
 154 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
 155 </rule>
 156 <rule>
 157 <id>Exceptions</id>
 158 <severity>OK</severity>
 159 <score>0.0</score>
 160 <shortDescription>The program generated 0 exceptions per second during 1.017 s starting at 4/26/18 12:10:30 PM.</shortDescription>
 161 <longDescription>The program generated 0 exceptions per second during 1.017 s starting at 4/26/18 12:10:30 PM.</longDescription>
 162 </rule>
 163 <rule>







 164 <id>FewSampledThreads</id>
 165 <severity>Information</severity>
 166 <score>29.510744962334375</score>
 167 <shortDescription>There are fewer sampled threads than the total number of hardware threads (cores).</shortDescription>
 168 <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>
 169 </rule>
 170 <rule>
 171 <id>FileRead</id>
 172 <severity>OK</severity>
 173 <score>0.0</score>
 174 <shortDescription>There are no file read events in this recording.</shortDescription>
 175 <longDescription>There are no file read events in this recording.</longDescription>
 176 </rule>
 177 <rule>
 178 <id>FileWrite</id>
 179 <severity>Not Applicable</severity>
 180 <score>-1.0</score>
 181 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>
 182 <longDescription>The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.&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>
 183 </rule>


 532 <severity>OK</severity>
 533 <score>0.0</score>
 534 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
 535 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
 536 </rule>
 537 <rule>
 538 <id>Errors</id>
 539 <severity>Not Applicable</severity>
 540 <score>-1.0</score>
 541 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
 542 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
 543 </rule>
 544 <rule>
 545 <id>Exceptions</id>
 546 <severity>OK</severity>
 547 <score>0.0</score>
 548 <shortDescription>The program generated 0 exceptions per second during 1.210 s starting at 4/26/18 12:12:47 PM.</shortDescription>
 549 <longDescription>The program generated 0 exceptions per second during 1.210 s starting at 4/26/18 12:12:47 PM.</longDescription>
 550 </rule>
 551 <rule>







 552 <id>FewSampledThreads</id>
 553 <severity>Information</severity>
 554 <score>29.510744962334375</score>
 555 <shortDescription>There are fewer sampled threads than the total number of hardware threads (cores).</shortDescription>
 556 <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>
 557 </rule>
 558 <rule>
 559 <id>FileRead</id>
 560 <severity>OK</severity>
 561 <score>0.0</score>
 562 <shortDescription>There are no file read events in this recording.</shortDescription>
 563 <longDescription>There are no file read events in this recording.</longDescription>
 564 </rule>
 565 <rule>
 566 <id>FileWrite</id>
 567 <severity>Not Applicable</severity>
 568 <score>-1.0</score>
 569 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>
 570 <longDescription>The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.&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>
 571 </rule>


 920 <severity>OK</severity>
 921 <score>0.0</score>
 922 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
 923 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
 924 </rule>
 925 <rule>
 926 <id>Errors</id>
 927 <severity>Not Applicable</severity>
 928 <score>-1.0</score>
 929 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
 930 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
 931 </rule>
 932 <rule>
 933 <id>Exceptions</id>
 934 <severity>Not Applicable</severity>
 935 <score>-1.0</score>
 936 <shortDescription>This rule requires events to be available from the following event types: 'Exception Statistics'.</shortDescription>
 937 <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>
 938 </rule>
 939 <rule>







 940 <id>FewSampledThreads</id>
 941 <severity>Not Applicable</severity>
 942 <score>-1.0</score>
 943 <shortDescription>This rule requires events to be available from the following event types: 'CPU Information', 'Method Profiling Sample', 'Recording Setting'.</shortDescription>
 944 <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>
 945 </rule>
 946 <rule>
 947 <id>FileRead</id>
 948 <severity>OK</severity>
 949 <score>0.0</score>
 950 <shortDescription>There are no file read events in this recording.</shortDescription>
 951 <longDescription>There are no file read events in this recording.</longDescription>
 952 </rule>
 953 <rule>
 954 <id>FileWrite</id>
 955 <severity>Not Applicable</severity>
 956 <score>-1.0</score>
 957 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>
 958 <longDescription>The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.&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>
 959 </rule>


1308 <severity>OK</severity>
1309 <score>0.0</score>
1310 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
1311 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
1312 </rule>
1313 <rule>
1314 <id>Errors</id>
1315 <severity>Not Applicable</severity>
1316 <score>-1.0</score>
1317 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
1318 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
1319 </rule>
1320 <rule>
1321 <id>Exceptions</id>
1322 <severity>OK</severity>
1323 <score>0.0</score>
1324 <shortDescription>The program generated 0 exceptions per second during 1.000 s starting at 4/25/18 11:38:36 AM.</shortDescription>
1325 <longDescription>The program generated 0 exceptions per second during 1.000 s starting at 4/25/18 11:38:36 AM.</longDescription>
1326 </rule>
1327 <rule>







1328 <id>FewSampledThreads</id>
1329 <severity>Not Applicable</severity>
1330 <score>-1.0</score>
1331 <shortDescription>This rule requires events to be available from the following event types: 'CPU Information', 'Method Profiling Sample', 'Recording Setting'.</shortDescription>
1332 <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>
1333 </rule>
1334 <rule>
1335 <id>FileRead</id>
1336 <severity>Not Applicable</severity>
1337 <score>-1.0</score>
1338 <shortDescription>This rule requires that the following event types are enabled: 'File Read'.</shortDescription>
1339 <longDescription>The File Read Peak Duration rule requires that the following event types are enabled: 'File Read'.&lt;p&gt;If you are using JMC to create a flight recording, then you can enable 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>
1340 </rule>
1341 <rule>
1342 <id>FileWrite</id>
1343 <severity>Not Applicable</severity>
1344 <score>-1.0</score>
1345 <shortDescription>This rule requires that the following event types are enabled: 'File Write'.</shortDescription>
1346 <longDescription>The File Write Peak Duration rule requires that the following event types are enabled: 'File Write'.&lt;p&gt;If you are using JMC to create a flight recording, then you can enable 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>
1347 </rule>


1696 <severity>OK</severity>
1697 <score>0.0</score>
1698 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
1699 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
1700 </rule>
1701 <rule>
1702 <id>Errors</id>
1703 <severity>Not Applicable</severity>
1704 <score>-1.0</score>
1705 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
1706 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
1707 </rule>
1708 <rule>
1709 <id>Exceptions</id>
1710 <severity>OK</severity>
1711 <score>0.0</score>
1712 <shortDescription>The program generated 0 exceptions per second during 999.487 ms starting at 4/4/14 11:17:06 AM.</shortDescription>
1713 <longDescription>The program generated 0 exceptions per second during 999.487 ms starting at 4/4/14 11:17:06 AM.</longDescription>
1714 </rule>
1715 <rule>







1716 <id>FewSampledThreads</id>
1717 <severity>OK</severity>
1718 <score>0.0</score>
1719 <shortDescription>There were no problems with the amount of sampled threads.</shortDescription>
1720 <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>
1721 </rule>
1722 <rule>
1723 <id>FileRead</id>
1724 <severity>OK</severity>
1725 <score>0.0</score>
1726 <shortDescription>There are no file read events in this recording.</shortDescription>
1727 <longDescription>There are no file read events in this recording.</longDescription>
1728 </rule>
1729 <rule>
1730 <id>FileWrite</id>
1731 <severity>Not Applicable</severity>
1732 <score>-1.0</score>
1733 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>
1734 <longDescription>The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.&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>
1735 </rule>


2084 <severity>OK</severity>
2085 <score>0.0</score>
2086 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
2087 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
2088 </rule>
2089 <rule>
2090 <id>Errors</id>
2091 <severity>Not Applicable</severity>
2092 <score>-1.0</score>
2093 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
2094 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
2095 </rule>
2096 <rule>
2097 <id>Exceptions</id>
2098 <severity>OK</severity>
2099 <score>0.0</score>
2100 <shortDescription>The program generated 0 exceptions per second during 1.009 s starting at 4/4/14 8:54:34 AM.</shortDescription>
2101 <longDescription>The program generated 0 exceptions per second during 1.009 s starting at 4/4/14 8:54:34 AM.</longDescription>
2102 </rule>
2103 <rule>







2104 <id>FewSampledThreads</id>
2105 <severity>OK</severity>
2106 <score>0.0</score>
2107 <shortDescription>There were no problems with the amount of sampled threads.</shortDescription>
2108 <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>
2109 </rule>
2110 <rule>
2111 <id>FileRead</id>
2112 <severity>OK</severity>
2113 <score>0.0</score>
2114 <shortDescription>There are no file read events in this recording.</shortDescription>
2115 <longDescription>There are no file read events in this recording.</longDescription>
2116 </rule>
2117 <rule>
2118 <id>FileWrite</id>
2119 <severity>Not Applicable</severity>
2120 <score>-1.0</score>
2121 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>
2122 <longDescription>The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.&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>
2123 </rule>


2472 <severity>OK</severity>
2473 <score>0.0</score>
2474 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
2475 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
2476 </rule>
2477 <rule>
2478 <id>Errors</id>
2479 <severity>Not Applicable</severity>
2480 <score>-1.0</score>
2481 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
2482 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
2483 </rule>
2484 <rule>
2485 <id>Exceptions</id>
2486 <severity>OK</severity>
2487 <score>0.0</score>
2488 <shortDescription>The program generated 0 exceptions per second during 1.054 s starting at 4/24/18 10:08:53 AM.</shortDescription>
2489 <longDescription>The program generated 0 exceptions per second during 1.054 s starting at 4/24/18 10:08:53 AM.</longDescription>
2490 </rule>
2491 <rule>







2492 <id>FewSampledThreads</id>
2493 <severity>Information</severity>
2494 <score>29.510744962334375</score>
2495 <shortDescription>There are fewer sampled threads than the total number of hardware threads (cores).</shortDescription>
2496 <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>
2497 </rule>
2498 <rule>
2499 <id>FileRead</id>
2500 <severity>OK</severity>
2501 <score>0.0</score>
2502 <shortDescription>There are no file read events in this recording.</shortDescription>
2503 <longDescription>There are no file read events in this recording.</longDescription>
2504 </rule>
2505 <rule>
2506 <id>FileWrite</id>
2507 <severity>Not Applicable</severity>
2508 <score>-1.0</score>
2509 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>
2510 <longDescription>The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.&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>
2511 </rule>


2860 <severity>Information</severity>
2861 <score>50.0</score>
2862 <shortDescription>There were 2 JVM duplicated flags.</shortDescription>
2863 <longDescription>There were 2 JVM duplicated flags. Duplicated JVM flags may be caused by multiple layers of scripts used when launching the application. Having duplicate flags is dangerous as changing one of the flags in one of the scripts may not have the intended effect. This can be especially dangerous for security related system properties. Try to find all the places where the flag is defined and keep only one. The following flags were duplicated: &lt;ul&gt;&lt;li&gt;Xverify&lt;/li&gt;&lt;li&gt;Djava.endorsed.dirs&lt;/li&gt;&lt;/ul&gt;</longDescription>
2864 </rule>
2865 <rule>
2866 <id>Errors</id>
2867 <severity>OK</severity>
2868 <score>14.166666666666668</score>
2869 <shortDescription>The program generated an average of 17 errors per minute during 9/24/2015 10:08:14 AM – 10:09:14 AM.</shortDescription>
2870 <longDescription>The program generated an average of 17 errors per minute during 9/24/2015 10:08:14 AM – 10:09:14 AM, 17 errors were thrown in total.&lt;p&gt;The most common error was 'java.lang.NoSuchMethodError', which was thrown 13 times.&lt;p&gt;Investigate the thrown errors to see if they can be avoided. Errors indicate that something went wrong with the code execution and should never be used for flow control. The following regular expression was used to exclude 381 errors from this rule: '(com.sun.el.parser.ELParser\$LookaheadSuccess)'.</longDescription>
2871 </rule>
2872 <rule>
2873 <id>Exceptions</id>
2874 <severity>OK</severity>
2875 <score>2.573808918421875</score>
2876 <shortDescription>The program generated 515 exceptions per second during 28.060 s starting at 9/24/15 10:08:58 AM.</shortDescription>
2877 <longDescription>The program generated 515 exceptions per second during 28.060 s starting at 9/24/15 10:08:58 AM.</longDescription>
2878 </rule>
2879 <rule>







2880 <id>FewSampledThreads</id>
2881 <severity>OK</severity>
2882 <score>0.0</score>
2883 <shortDescription>There were no problems with the amount of sampled threads.</shortDescription>
2884 <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>
2885 </rule>
2886 <rule>
2887 <id>FileRead</id>
2888 <severity>OK</severity>
2889 <score>0.2033639625</score>
2890 <shortDescription>No long file read pauses were found in this recording (the longest was 16.269 ms).</shortDescription>
2891 <longDescription>No long file read pauses were found in this recording (the longest was 16.269 ms).</longDescription>
2892 </rule>
2893 <rule>
2894 <id>FileWrite</id>
2895 <severity>OK</severity>
2896 <score>2.1551020875</score>
2897 <shortDescription>No long file write pauses were found in this recording (the longest was 172.408 ms).</shortDescription>
2898 <longDescription>No long file write pauses were found in this recording (the longest was 172.408 ms).</longDescription>
2899 </rule>


3248 <rule>
3249 <id>DuplicateFlags</id>
3250 <severity>Information</severity>
3251 <score>50.0</score>
3252 <shortDescription>There were 6 JVM duplicated flags.</shortDescription>
3253 <longDescription>There were 6 JVM duplicated flags. Duplicated JVM flags may be caused by multiple layers of scripts used when launching the application. Having duplicate flags is dangerous as changing one of the flags in one of the scripts may not have the intended effect. This can be especially dangerous for security related system properties. Try to find all the places where the flag is defined and keep only one. The following flags were duplicated: &lt;ul&gt;&lt;li&gt;Xmx&lt;/li&gt;&lt;li&gt;NewSize&lt;/li&gt;&lt;li&gt;Dweblogic.home&lt;/li&gt;&lt;li&gt;-add-opens&lt;/li&gt;&lt;li&gt;MaxNewSize&lt;/li&gt;&lt;li&gt;Xms&lt;/li&gt;&lt;/ul&gt;</longDescription>
3254 </rule>
3255 <rule>
3256 <id>Errors</id>
3257 <severity>Not Applicable</severity>
3258 <score>-1.0</score>
3259 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
3260 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
3261 </rule>
3262 <rule>
3263 <id>Exceptions</id>
3264 <severity>Not Applicable</severity>
3265 <score>-1.0</score>
3266 <shortDescription>This rule requires events to be available from the following event types: 'Exception Statistics'.</shortDescription>
3267 <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>







3268 </rule>
3269 <rule>
3270 <id>FewSampledThreads</id>
3271 <severity>Not Applicable</severity>
3272 <score>-1.0</score>
3273 <shortDescription>This rule requires events to be available from the following event types: 'CPU Information', 'Method Profiling Sample', 'Recording Setting'.</shortDescription>
3274 <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>
3275 </rule>
3276 <rule>
3277 <id>FileRead</id>
3278 <severity>OK</severity>
3279 <score>0.0</score>
3280 <shortDescription>There are no file read events in this recording.</shortDescription>
3281 <longDescription>There are no file read events in this recording.</longDescription>
3282 </rule>
3283 <rule>
3284 <id>FileWrite</id>
3285 <severity>Not Applicable</severity>
3286 <score>-1.0</score>
3287 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>




 144 <severity>OK</severity>
 145 <score>0.0</score>
 146 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
 147 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
 148 </rule>
 149 <rule>
 150 <id>Errors</id>
 151 <severity>Not Applicable</severity>
 152 <score>-1.0</score>
 153 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
 154 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
 155 </rule>
 156 <rule>
 157 <id>Exceptions</id>
 158 <severity>OK</severity>
 159 <score>0.0</score>
 160 <shortDescription>The program generated 0 exceptions per second during 1.017 s starting at 4/26/18 12:10:30 PM.</shortDescription>
 161 <longDescription>The program generated 0 exceptions per second during 1.017 s starting at 4/26/18 12:10:30 PM.</longDescription>
 162 </rule>
 163 <rule>
 164 <id>Fatal Errors</id>
 165 <severity>Not Applicable</severity>
 166 <score>-1.0</score>
 167 <shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
 168 <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>
 169 </rule>
 170 <rule>
 171 <id>FewSampledThreads</id>
 172 <severity>Information</severity>
 173 <score>29.510744962334375</score>
 174 <shortDescription>There are fewer sampled threads than the total number of hardware threads (cores).</shortDescription>
 175 <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>
 176 </rule>
 177 <rule>
 178 <id>FileRead</id>
 179 <severity>OK</severity>
 180 <score>0.0</score>
 181 <shortDescription>There are no file read events in this recording.</shortDescription>
 182 <longDescription>There are no file read events in this recording.</longDescription>
 183 </rule>
 184 <rule>
 185 <id>FileWrite</id>
 186 <severity>Not Applicable</severity>
 187 <score>-1.0</score>
 188 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>
 189 <longDescription>The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.&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>
 190 </rule>


 539 <severity>OK</severity>
 540 <score>0.0</score>
 541 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
 542 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
 543 </rule>
 544 <rule>
 545 <id>Errors</id>
 546 <severity>Not Applicable</severity>
 547 <score>-1.0</score>
 548 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
 549 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
 550 </rule>
 551 <rule>
 552 <id>Exceptions</id>
 553 <severity>OK</severity>
 554 <score>0.0</score>
 555 <shortDescription>The program generated 0 exceptions per second during 1.210 s starting at 4/26/18 12:12:47 PM.</shortDescription>
 556 <longDescription>The program generated 0 exceptions per second during 1.210 s starting at 4/26/18 12:12:47 PM.</longDescription>
 557 </rule>
 558 <rule>
 559 <id>Fatal Errors</id>
 560 <severity>Not Applicable</severity>
 561 <score>-1.0</score>
 562 <shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
 563 <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>
 564 </rule>
 565 <rule>
 566 <id>FewSampledThreads</id>
 567 <severity>Information</severity>
 568 <score>29.510744962334375</score>
 569 <shortDescription>There are fewer sampled threads than the total number of hardware threads (cores).</shortDescription>
 570 <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>
 571 </rule>
 572 <rule>
 573 <id>FileRead</id>
 574 <severity>OK</severity>
 575 <score>0.0</score>
 576 <shortDescription>There are no file read events in this recording.</shortDescription>
 577 <longDescription>There are no file read events in this recording.</longDescription>
 578 </rule>
 579 <rule>
 580 <id>FileWrite</id>
 581 <severity>Not Applicable</severity>
 582 <score>-1.0</score>
 583 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>
 584 <longDescription>The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.&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>
 585 </rule>


 934 <severity>OK</severity>
 935 <score>0.0</score>
 936 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
 937 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
 938 </rule>
 939 <rule>
 940 <id>Errors</id>
 941 <severity>Not Applicable</severity>
 942 <score>-1.0</score>
 943 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
 944 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
 945 </rule>
 946 <rule>
 947 <id>Exceptions</id>
 948 <severity>Not Applicable</severity>
 949 <score>-1.0</score>
 950 <shortDescription>This rule requires events to be available from the following event types: 'Exception Statistics'.</shortDescription>
 951 <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>
 952 </rule>
 953 <rule>
 954 <id>Fatal Errors</id>
 955 <severity>Not Applicable</severity>
 956 <score>-1.0</score>
 957 <shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
 958 <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>
 959 </rule>
 960 <rule>
 961 <id>FewSampledThreads</id>
 962 <severity>Not Applicable</severity>
 963 <score>-1.0</score>
 964 <shortDescription>This rule requires events to be available from the following event types: 'CPU Information', 'Method Profiling Sample', 'Recording Setting'.</shortDescription>
 965 <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>
 966 </rule>
 967 <rule>
 968 <id>FileRead</id>
 969 <severity>OK</severity>
 970 <score>0.0</score>
 971 <shortDescription>There are no file read events in this recording.</shortDescription>
 972 <longDescription>There are no file read events in this recording.</longDescription>
 973 </rule>
 974 <rule>
 975 <id>FileWrite</id>
 976 <severity>Not Applicable</severity>
 977 <score>-1.0</score>
 978 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>
 979 <longDescription>The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.&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>
 980 </rule>


1329 <severity>OK</severity>
1330 <score>0.0</score>
1331 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
1332 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
1333 </rule>
1334 <rule>
1335 <id>Errors</id>
1336 <severity>Not Applicable</severity>
1337 <score>-1.0</score>
1338 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
1339 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
1340 </rule>
1341 <rule>
1342 <id>Exceptions</id>
1343 <severity>OK</severity>
1344 <score>0.0</score>
1345 <shortDescription>The program generated 0 exceptions per second during 1.000 s starting at 4/25/18 11:38:36 AM.</shortDescription>
1346 <longDescription>The program generated 0 exceptions per second during 1.000 s starting at 4/25/18 11:38:36 AM.</longDescription>
1347 </rule>
1348 <rule>
1349 <id>Fatal Errors</id>
1350 <severity>Not Applicable</severity>
1351 <score>-1.0</score>
1352 <shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
1353 <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>
1354 </rule>
1355 <rule>
1356 <id>FewSampledThreads</id>
1357 <severity>Not Applicable</severity>
1358 <score>-1.0</score>
1359 <shortDescription>This rule requires events to be available from the following event types: 'CPU Information', 'Method Profiling Sample', 'Recording Setting'.</shortDescription>
1360 <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>
1361 </rule>
1362 <rule>
1363 <id>FileRead</id>
1364 <severity>Not Applicable</severity>
1365 <score>-1.0</score>
1366 <shortDescription>This rule requires that the following event types are enabled: 'File Read'.</shortDescription>
1367 <longDescription>The File Read Peak Duration rule requires that the following event types are enabled: 'File Read'.&lt;p&gt;If you are using JMC to create a flight recording, then you can enable 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>
1368 </rule>
1369 <rule>
1370 <id>FileWrite</id>
1371 <severity>Not Applicable</severity>
1372 <score>-1.0</score>
1373 <shortDescription>This rule requires that the following event types are enabled: 'File Write'.</shortDescription>
1374 <longDescription>The File Write Peak Duration rule requires that the following event types are enabled: 'File Write'.&lt;p&gt;If you are using JMC to create a flight recording, then you can enable 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>
1375 </rule>


1724 <severity>OK</severity>
1725 <score>0.0</score>
1726 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
1727 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
1728 </rule>
1729 <rule>
1730 <id>Errors</id>
1731 <severity>Not Applicable</severity>
1732 <score>-1.0</score>
1733 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
1734 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
1735 </rule>
1736 <rule>
1737 <id>Exceptions</id>
1738 <severity>OK</severity>
1739 <score>0.0</score>
1740 <shortDescription>The program generated 0 exceptions per second during 999.487 ms starting at 4/4/14 11:17:06 AM.</shortDescription>
1741 <longDescription>The program generated 0 exceptions per second during 999.487 ms starting at 4/4/14 11:17:06 AM.</longDescription>
1742 </rule>
1743 <rule>
1744 <id>Fatal Errors</id>
1745 <severity>Not Applicable</severity>
1746 <score>-1.0</score>
1747 <shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
1748 <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>
1749 </rule>
1750 <rule>
1751 <id>FewSampledThreads</id>
1752 <severity>OK</severity>
1753 <score>0.0</score>
1754 <shortDescription>There were no problems with the amount of sampled threads.</shortDescription>
1755 <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>
1756 </rule>
1757 <rule>
1758 <id>FileRead</id>
1759 <severity>OK</severity>
1760 <score>0.0</score>
1761 <shortDescription>There are no file read events in this recording.</shortDescription>
1762 <longDescription>There are no file read events in this recording.</longDescription>
1763 </rule>
1764 <rule>
1765 <id>FileWrite</id>
1766 <severity>Not Applicable</severity>
1767 <score>-1.0</score>
1768 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>
1769 <longDescription>The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.&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>
1770 </rule>


2119 <severity>OK</severity>
2120 <score>0.0</score>
2121 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
2122 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
2123 </rule>
2124 <rule>
2125 <id>Errors</id>
2126 <severity>Not Applicable</severity>
2127 <score>-1.0</score>
2128 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
2129 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
2130 </rule>
2131 <rule>
2132 <id>Exceptions</id>
2133 <severity>OK</severity>
2134 <score>0.0</score>
2135 <shortDescription>The program generated 0 exceptions per second during 1.009 s starting at 4/4/14 8:54:34 AM.</shortDescription>
2136 <longDescription>The program generated 0 exceptions per second during 1.009 s starting at 4/4/14 8:54:34 AM.</longDescription>
2137 </rule>
2138 <rule>
2139 <id>Fatal Errors</id>
2140 <severity>Not Applicable</severity>
2141 <score>-1.0</score>
2142 <shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
2143 <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>
2144 </rule>
2145 <rule>
2146 <id>FewSampledThreads</id>
2147 <severity>OK</severity>
2148 <score>0.0</score>
2149 <shortDescription>There were no problems with the amount of sampled threads.</shortDescription>
2150 <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>
2151 </rule>
2152 <rule>
2153 <id>FileRead</id>
2154 <severity>OK</severity>
2155 <score>0.0</score>
2156 <shortDescription>There are no file read events in this recording.</shortDescription>
2157 <longDescription>There are no file read events in this recording.</longDescription>
2158 </rule>
2159 <rule>
2160 <id>FileWrite</id>
2161 <severity>Not Applicable</severity>
2162 <score>-1.0</score>
2163 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>
2164 <longDescription>The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.&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>
2165 </rule>


2514 <severity>OK</severity>
2515 <score>0.0</score>
2516 <shortDescription>There were no duplicate JVM flags on the command line.</shortDescription>
2517 <longDescription>There were no duplicate JVM flags on the command line.</longDescription>
2518 </rule>
2519 <rule>
2520 <id>Errors</id>
2521 <severity>Not Applicable</severity>
2522 <score>-1.0</score>
2523 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
2524 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
2525 </rule>
2526 <rule>
2527 <id>Exceptions</id>
2528 <severity>OK</severity>
2529 <score>0.0</score>
2530 <shortDescription>The program generated 0 exceptions per second during 1.054 s starting at 4/24/18 10:08:53 AM.</shortDescription>
2531 <longDescription>The program generated 0 exceptions per second during 1.054 s starting at 4/24/18 10:08:53 AM.</longDescription>
2532 </rule>
2533 <rule>
2534 <id>Fatal Errors</id>
2535 <severity>Not Applicable</severity>
2536 <score>-1.0</score>
2537 <shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
2538 <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>
2539 </rule>
2540 <rule>
2541 <id>FewSampledThreads</id>
2542 <severity>Information</severity>
2543 <score>29.510744962334375</score>
2544 <shortDescription>There are fewer sampled threads than the total number of hardware threads (cores).</shortDescription>
2545 <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>
2546 </rule>
2547 <rule>
2548 <id>FileRead</id>
2549 <severity>OK</severity>
2550 <score>0.0</score>
2551 <shortDescription>There are no file read events in this recording.</shortDescription>
2552 <longDescription>There are no file read events in this recording.</longDescription>
2553 </rule>
2554 <rule>
2555 <id>FileWrite</id>
2556 <severity>Not Applicable</severity>
2557 <score>-1.0</score>
2558 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>
2559 <longDescription>The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.&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>
2560 </rule>


2909 <severity>Information</severity>
2910 <score>50.0</score>
2911 <shortDescription>There were 2 JVM duplicated flags.</shortDescription>
2912 <longDescription>There were 2 JVM duplicated flags. Duplicated JVM flags may be caused by multiple layers of scripts used when launching the application. Having duplicate flags is dangerous as changing one of the flags in one of the scripts may not have the intended effect. This can be especially dangerous for security related system properties. Try to find all the places where the flag is defined and keep only one. The following flags were duplicated: &lt;ul&gt;&lt;li&gt;Xverify&lt;/li&gt;&lt;li&gt;Djava.endorsed.dirs&lt;/li&gt;&lt;/ul&gt;</longDescription>
2913 </rule>
2914 <rule>
2915 <id>Errors</id>
2916 <severity>OK</severity>
2917 <score>14.166666666666668</score>
2918 <shortDescription>The program generated an average of 17 errors per minute during 9/24/2015 10:08:14 AM – 10:09:14 AM.</shortDescription>
2919 <longDescription>The program generated an average of 17 errors per minute during 9/24/2015 10:08:14 AM – 10:09:14 AM, 17 errors were thrown in total.&lt;p&gt;The most common error was 'java.lang.NoSuchMethodError', which was thrown 13 times.&lt;p&gt;Investigate the thrown errors to see if they can be avoided. Errors indicate that something went wrong with the code execution and should never be used for flow control. The following regular expression was used to exclude 381 errors from this rule: '(com.sun.el.parser.ELParser\$LookaheadSuccess)'.</longDescription>
2920 </rule>
2921 <rule>
2922 <id>Exceptions</id>
2923 <severity>OK</severity>
2924 <score>2.573808918421875</score>
2925 <shortDescription>The program generated 515 exceptions per second during 28.060 s starting at 9/24/15 10:08:58 AM.</shortDescription>
2926 <longDescription>The program generated 515 exceptions per second during 28.060 s starting at 9/24/15 10:08:58 AM.</longDescription>
2927 </rule>
2928 <rule>
2929 <id>Fatal Errors</id>
2930 <severity>Not Applicable</severity>
2931 <score>-1.0</score>
2932 <shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
2933 <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>
2934 </rule>
2935 <rule>
2936 <id>FewSampledThreads</id>
2937 <severity>OK</severity>
2938 <score>0.0</score>
2939 <shortDescription>There were no problems with the amount of sampled threads.</shortDescription>
2940 <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>
2941 </rule>
2942 <rule>
2943 <id>FileRead</id>
2944 <severity>OK</severity>
2945 <score>0.2033639625</score>
2946 <shortDescription>No long file read pauses were found in this recording (the longest was 16.269 ms).</shortDescription>
2947 <longDescription>No long file read pauses were found in this recording (the longest was 16.269 ms).</longDescription>
2948 </rule>
2949 <rule>
2950 <id>FileWrite</id>
2951 <severity>OK</severity>
2952 <score>2.1551020875</score>
2953 <shortDescription>No long file write pauses were found in this recording (the longest was 172.408 ms).</shortDescription>
2954 <longDescription>No long file write pauses were found in this recording (the longest was 172.408 ms).</longDescription>
2955 </rule>


3304 <rule>
3305 <id>DuplicateFlags</id>
3306 <severity>Information</severity>
3307 <score>50.0</score>
3308 <shortDescription>There were 6 JVM duplicated flags.</shortDescription>
3309 <longDescription>There were 6 JVM duplicated flags. Duplicated JVM flags may be caused by multiple layers of scripts used when launching the application. Having duplicate flags is dangerous as changing one of the flags in one of the scripts may not have the intended effect. This can be especially dangerous for security related system properties. Try to find all the places where the flag is defined and keep only one. The following flags were duplicated: &lt;ul&gt;&lt;li&gt;Xmx&lt;/li&gt;&lt;li&gt;NewSize&lt;/li&gt;&lt;li&gt;Dweblogic.home&lt;/li&gt;&lt;li&gt;-add-opens&lt;/li&gt;&lt;li&gt;MaxNewSize&lt;/li&gt;&lt;li&gt;Xms&lt;/li&gt;&lt;/ul&gt;</longDescription>
3310 </rule>
3311 <rule>
3312 <id>Errors</id>
3313 <severity>Not Applicable</severity>
3314 <score>-1.0</score>
3315 <shortDescription>This rule requires events to be available from the following event types: 'Java Error'.</shortDescription>
3316 <longDescription>The Thrown Errors rule requires events to be available from the following event types: 'Java Error'.&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>
3317 </rule>
3318 <rule>
3319 <id>Exceptions</id>
3320 <severity>Not Applicable</severity>
3321 <score>-1.0</score>
3322 <shortDescription>This rule requires events to be available from the following event types: 'Exception Statistics'.</shortDescription>
3323 <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>
3324 </rule>
3325 <rule>
3326 <id>Fatal Errors</id>
3327 <severity>Not Applicable</severity>
3328 <score>-1.0</score>
3329 <shortDescription>The Fatal Errors rule requires the following event types: 'jdk.Shutdown'.</shortDescription>
3330 <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>
3331 </rule>
3332 <rule>
3333 <id>FewSampledThreads</id>
3334 <severity>Not Applicable</severity>
3335 <score>-1.0</score>
3336 <shortDescription>This rule requires events to be available from the following event types: 'CPU Information', 'Method Profiling Sample', 'Recording Setting'.</shortDescription>
3337 <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>
3338 </rule>
3339 <rule>
3340 <id>FileRead</id>
3341 <severity>OK</severity>
3342 <score>0.0</score>
3343 <shortDescription>There are no file read events in this recording.</shortDescription>
3344 <longDescription>There are no file read events in this recording.</longDescription>
3345 </rule>
3346 <rule>
3347 <id>FileWrite</id>
3348 <severity>Not Applicable</severity>
3349 <score>-1.0</score>
3350 <shortDescription>This rule requires events to be available from the following event types: 'File Write'.</shortDescription>


< prev index next >