1 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
2 <!--
3 Copyright (c) 2018, Oracle and/or its affiliates. All rights reserved.
4
5 DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
6
7 The contents of this file are subject to the terms of either the Universal Permissive License
8 v 1.0 as shown at http://oss.oracle.com/licenses/upl
9
10 or the following license:
11
12 Redistribution and use in source and binary forms, with or without modification, are permitted
13 provided that the following conditions are met:
14
15 1. Redistributions of source code must retain the above copyright notice, this list of conditions
16 and the following disclaimer.
17
18 2. Redistributions in binary form must reproduce the above copyright notice, this list of
19 conditions and the following disclaimer in the documentation and/or other materials provided with
20 the distribution.
21
22 3. Neither the name of the copyright holder nor the names of its contributors may be used to
23 endorse or promote products derived from this software without specific prior written permission.
24
25 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
26 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
27 FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
28 CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
29 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
30 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
31 WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
32 WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
33 -->
34 <reportcollection>
35 <report>
36 <file>allocation_10s_before.jfr</file>
37 <rule>
38 <id>Allocations.class</id>
39 <severity>Information</severity>
40 <score>66.39548837411446</score>
41 <shortDescription>The most allocated class is likely 'java.lang.Integer'. This is the most common allocation path for that class: <ul><li>Integer.valueOf(int) (100 %)</li><li>Allocator.go()</li><li>Allocator.main(String[])</li></ul></shortDescription>
42 <longDescription>The most allocated class is likely 'java.lang.Integer'. This is the most common allocation path for that class: <ul><li>Integer.valueOf(int) (100 %)</li><li>Allocator.go()</li><li>Allocator.main(String[])</li></ul><p>Frequently allocated classes are likely good places to start when trying to reduce garbage collections. Look at the aggregated stack traces of the most commonly allocated classes to see if many instances are created along the same call path. Try to reduce the number of instances created by invoking the most commonly taken paths less.</longDescription>
43 </rule>
44 <rule>
45 <id>Allocations.thread</id>
46 <severity>Information</severity>
47 <score>66.40149861711905</score>
48 <shortDescription>The thread performing the most allocation is likely 'main'. This is the most common allocation path for that class: <ul><li>Integer.valueOf(int) (100 %)</li><li>Allocator.go()</li><li>Allocator.main(String[])</li></ul></shortDescription>
49 <longDescription>The thread performing the most allocation is likely 'main'. This is the most common allocation path for that class: <ul><li>Integer.valueOf(int) (100 %)</li><li>Allocator.go()</li><li>Allocator.main(String[])</li></ul><p>Many allocations performed by the same thread might indicate a problem in a multi-threaded program. Look at the aggregated stack traces for the thread with the highest allocation rate. See if the allocation rate can be brought down, or balanced among the active threads.</longDescription>
50 </rule>
51 <rule>
52 <id>ApplicationHalts</id>
53 <severity>OK</severity>
54 <score>0.9591288888888891</score>
55 <shortDescription>Application efficiency was not highly affected by halts.</shortDescription>
56 <longDescription>Application efficiency was not highly affected by halts.<p>The highest ratio between application halts and execution time was 0.192 % during 1 min starting at 4/26/18 12:10:29 PM. 28.068 % of the halts during the timespan were because of other reasons than GCs.<p>The total halts ratio during the entire recording was 1.162 %. 28.068 % of the total halts were because of other reasons than GCs.</longDescription>
57 </rule>
58 <rule>
59 <id>BufferLost</id>
60 <severity>OK</severity>
61 <score>0.0</score>
62 <shortDescription>No Flight Recorder buffers were lost during the recording.</shortDescription>
63 <longDescription>No Flight Recorder buffers were lost during the recording.</longDescription>
64 </rule>
65 <rule>
66 <id>BytecodeVerification</id>
67 <severity>OK</severity>
68 <score>0.0</score>
69 <shortDescription>The application was running with bytecode verification enabled.</shortDescription>
70 <longDescription>The application was running with bytecode verification enabled.</longDescription>
71 </rule>
72 <rule>
73 <id>ClassLeak</id>
74 <severity>Not Applicable</severity>
75 <score>-1.0</score>
76 <shortDescription>This rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.</shortDescription>
77 <longDescription>The Class Leak rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
78 </rule>
79 <rule>
80 <id>ClassLoading</id>
81 <severity>Not Applicable</severity>
82 <score>-1.0</score>
83 <shortDescription>This rule requires that the following event types are enabled: 'Class Load'.</shortDescription>
84 <longDescription>The Class Loading Pressure rule requires that the following event types are enabled: 'Class Load'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
85 </rule>
86 <rule>
87 <id>CodeCache</id>
88 <severity>OK</severity>
89 <score>21.736190753325</score>
90 <shortDescription>No problems with the code cache were detected in the recording.</shortDescription>
91 <longDescription>No problems with the code cache were detected in the recording.</longDescription>
92 </rule>
93 <rule>
94 <id>CompareCpu</id>
95 <severity>OK</severity>
96 <score>1.141997550803353</score>
97 <shortDescription>An average CPU load of 1 % was caused by other processes during 1.027 s starting at 4/26/18 12:10:33 PM.</shortDescription>
98 <longDescription>An average CPU load of 1 % was caused by other processes during 1.027 s starting at 4/26/18 12:10:33 PM.</longDescription>
99 </rule>
100 <rule>
101 <id>CompressedOops</id>
102 <severity>OK</severity>
103 <score>0.0</score>
104 <shortDescription>The settings for Compressed Oops were OK.</shortDescription>
105 <longDescription>The settings for Compressed Oops were OK.</longDescription>
106 </rule>
107 <rule>
108 <id>ContextSwitch</id>
109 <severity>Not Applicable</severity>
110 <score>-1.0</score>
111 <shortDescription>This rule requires events to be available from the following event types: 'Thread Context Switch Rate'.</shortDescription>
112 <longDescription>The Context Switches rule requires events to be available from the following event types: 'Thread Context Switch Rate'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
113 </rule>
114 <rule>
115 <id>DMSIncident</id>
116 <severity>Not Applicable</severity>
117 <score>-1.0</score>
118 <shortDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.</shortDescription>
119 <longDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.<p>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>
120 </rule>
121 <rule>
122 <id>DebugNonSafepoints</id>
123 <severity>OK</severity>
124 <score>0.0</score>
125 <shortDescription>DebugNonSafepoints was implicitly enabled in the JVM version used to create this recording.</shortDescription>
126 <longDescription>DebugNonSafepoints was implicitly enabled in the JVM version used to create this recording.</longDescription>
127 </rule>
128 <rule>
129 <id>DiscouragedVmOptions</id>
130 <severity>OK</severity>
131 <score>0.0</score>
132 <shortDescription>No problems were found with the VM options.</shortDescription>
133 <longDescription>No problems were found with the VM options.</longDescription>
134 </rule>
135 <rule>
136 <id>DumpReason</id>
137 <severity>OK</severity>
138 <score>0.0</score>
139 <shortDescription>This recording was not dumped for an exceptional reason.</shortDescription>
140 <longDescription>This recording was not dumped for an exceptional reason.</longDescription>
141 </rule>
142 <rule>
143 <id>DuplicateFlags</id>
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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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'.<p>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).<p>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.<p>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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
190 </rule>
191 <rule>
192 <id>FlightRecordingSupport</id>
193 <severity>OK</severity>
194 <score>0.0</score>
195 <shortDescription>The JVM version used for this recording has full Flight Recorder support.</shortDescription>
196 <longDescription>The JVM version used for this recording has full Flight Recorder support.</longDescription>
197 </rule>
198 <rule>
199 <id>GcFreedRatio</id>
200 <severity>Information</severity>
201 <score>34.4635049904725</score>
202 <shortDescription>The ratio between memory freed by garbage collections per second and liveset is 65. This may be excessive.</shortDescription>
203 <longDescription>242 MiB per second was freed by garbage collections during 10 s starting at 4/26/18 12:10:29 PM. This is 65.013 times the average liveset which was 3.72 MiB. This may be excessive.<p>If the garbage collector can free a lot of memory, it may be because the application allocates a lot of short lived objects. To decrease the allocation rate, investigate the allocation stack traces to see which code paths cause the most allocation.<p>This recording is only 9.903 s long, consider creating a recording longer than 20 s for improved rule accuracy.</longDescription>
204 </rule>
205 <rule>
206 <id>GcLocker</id>
207 <severity>OK</severity>
208 <score>0.0</score>
209 <shortDescription>The GC Locker did not cause any garbage collections.</shortDescription>
210 <longDescription>The GC Locker did not cause any garbage collections.</longDescription>
211 </rule>
212 <rule>
213 <id>GcOptions</id>
214 <severity>OK</severity>
215 <score>0.0</score>
216 <shortDescription>No problems were found with the GC configuration.</shortDescription>
217 <longDescription>No problems were found with the GC configuration.</longDescription>
218 </rule>
219 <rule>
220 <id>GcPauseRatio</id>
221 <severity>OK</severity>
222 <score>0.6899182222222222</score>
223 <shortDescription>Application efficiency was not highly affected by GC pauses.</shortDescription>
224 <longDescription>Application efficiency was not highly affected by GC pauses.<p>The highest ratio between garbage collection pauses and execution time was 0.138 % during 1 min starting at 4/26/18 12:10:29 PM. The garbage collection pause ratio of the entire recording was 0.836 %.</longDescription>
225 </rule>
226 <rule>
227 <id>GcStall</id>
228 <severity>Not Applicable</severity>
229 <score>-1.0</score>
230 <shortDescription>This rule requires events to be available from the following event types: 'Concurrent Mode Failure', 'GC Configuration', 'Garbage Collection'.</shortDescription>
231 <longDescription>The GC Stall rule requires events to be available from the following event types: 'Concurrent Mode Failure', 'GC Configuration', 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
232 </rule>
233 <rule>
234 <id>HeapContent</id>
235 <severity>Not Applicable</severity>
236 <score>-1.0</score>
237 <shortDescription>This rule requires that the following event types are enabled: 'Object Count'.</shortDescription>
238 <longDescription>The Heap Content rule requires that the following event types are enabled: 'Object Count'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
239 </rule>
240 <rule>
241 <id>HeapInspectionGc</id>
242 <severity>OK</severity>
243 <score>0.0</score>
244 <shortDescription>The JVM did not perform any heap inspection GCs.</shortDescription>
245 <longDescription>The JVM did not perform any heap inspection GCs. This is good since they usually take a lot of time.</longDescription>
246 </rule>
247 <rule>
248 <id>HighGc</id>
249 <severity>OK</severity>
250 <score>2.5016205991264973</score>
251 <shortDescription>The JVM was paused for 100 % of the time during 11.003 ms starting at 4/26/18 12:10:36 PM.</shortDescription>
252 <longDescription>The JVM was paused for 100 % of the time during 11.003 ms starting at 4/26/18 12:10:36 PM. The time spent performing garbage collection may be reduced by increasing the heap size or by trying to reduce allocation.</longDescription>
253 </rule>
254 <rule>
255 <id>HighJvmCpu</id>
256 <severity>OK</severity>
257 <score>1.3537208124606583</score>
258 <shortDescription>The JVM does not seem to cause a lot of CPU load.</shortDescription>
259 <longDescription>The JVM does not seem to cause a lot of CPU load.</longDescription>
260 </rule>
261 <rule>
262 <id>IncreasingLiveSet</id>
263 <severity>OK</severity>
264 <score>0.0</score>
265 <shortDescription>No memory leaks were detected.</shortDescription>
266 <longDescription>No memory leaks were detected.</longDescription>
267 </rule>
268 <rule>
269 <id>IncreasingMetaSpaceLiveSet</id>
270 <severity>OK</severity>
271 <score>0.0</score>
272 <shortDescription>The class data does not seem to increase during the recording.</shortDescription>
273 <longDescription>The class data does not seem to increase during the recording.</longDescription>
274 </rule>
275 <rule>
276 <id>JavaBlocking</id>
277 <severity>Not Applicable</severity>
278 <score>-1.0</score>
279 <shortDescription>This rule requires events to be available from the following event types: 'Java Monitor Blocked'.</shortDescription>
280 <longDescription>The Java Blocking rule requires events to be available from the following event types: 'Java Monitor Blocked'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
281 </rule>
282 <rule>
283 <id>LongGcPause</id>
284 <severity>OK</severity>
285 <score>0.3348866229800136</score>
286 <shortDescription>The longest GC pause was 11.003 ms.</shortDescription>
287 <longDescription>The longest GC pause was 11.003 ms.</longDescription>
288 </rule>
289 <rule>
290 <id>LowOnPhysicalMemory</id>
291 <severity>OK</severity>
292 <score>0.0</score>
293 <shortDescription>The system did not run low on physical memory during this recording.</shortDescription>
294 <longDescription>The system did not run low on physical memory during this recording.</longDescription>
295 </rule>
296 <rule>
297 <id>ManagementAgent</id>
298 <severity>Not Applicable</severity>
299 <score>-1.0</score>
300 <shortDescription>This rule requires that the following event types are enabled: 'Initial System Property'.</shortDescription>
301 <longDescription>The Discouraged Management Agent Settings rule requires that the following event types are enabled: 'Initial System Property'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
302 </rule>
303 <rule>
304 <id>ManyRunningProcesses</id>
305 <severity>Not Applicable</severity>
306 <score>-1.0</score>
307 <shortDescription>This rule requires that the following event types are enabled: 'System Process'.</shortDescription>
308 <longDescription>The Competing Processes rule requires that the following event types are enabled: 'System Process'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
309 </rule>
310 <rule>
311 <id>MetaspaceOom</id>
312 <severity>OK</severity>
313 <score>0.0</score>
314 <shortDescription>The metaspace was not exhausted during this recording.</shortDescription>
315 <longDescription>The metaspace was not exhausted during this recording.</longDescription>
316 </rule>
317 <rule>
318 <id>MethodProfiling</id>
319 <severity>OK</severity>
320 <score>0.0</score>
321 <shortDescription>No methods where optimization would be particularly efficient could be detected.</shortDescription>
322 <longDescription>No methods where optimization would be particularly efficient could be detected.</longDescription>
323 </rule>
324 <rule>
325 <id>Options</id>
326 <severity>OK</severity>
327 <score>0.0</score>
328 <shortDescription>No undocumented, deprecated or non-recommended option flags were detected.</shortDescription>
329 <longDescription>No undocumented, deprecated or non-recommended option flags were detected.</longDescription>
330 </rule>
331 <rule>
332 <id>OverAggressiveRecordingSetting</id>
333 <severity>Not Applicable</severity>
334 <score>-1.0</score>
335 <shortDescription>This rule requires that the following event types are enabled: 'Initial System Property'.</shortDescription>
336 <longDescription>The Discouraged Recording Settings rule requires that the following event types are enabled: 'Initial System Property'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
337 </rule>
338 <rule>
339 <id>PasswordsInArguments</id>
340 <severity>OK</severity>
341 <score>0.0</score>
342 <shortDescription>The recording does not seem to contain passwords in the application arguments.</shortDescription>
343 <longDescription>The recording does not seem to contain passwords in the application arguments.</longDescription>
344 </rule>
345 <rule>
346 <id>PasswordsInEnvironment</id>
347 <severity>Not Applicable</severity>
348 <score>-1.0</score>
349 <shortDescription>This rule requires that the following event types are enabled: 'Initial Environment Variable'.</shortDescription>
350 <longDescription>The Passwords in Environment Variables rule requires that the following event types are enabled: 'Initial Environment Variable'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
351 </rule>
352 <rule>
353 <id>PasswordsInSystemProperties</id>
354 <severity>Not Applicable</severity>
355 <score>-1.0</score>
356 <shortDescription>This rule requires that the following event types are enabled: 'Initial System Property'.</shortDescription>
357 <longDescription>The Passwords in System Properties rule requires that the following event types are enabled: 'Initial System Property'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
358 </rule>
359 <rule>
360 <id>PrimitiveToObjectConversion</id>
361 <severity>Not Applicable</severity>
362 <score>-1.0</score>
363 <shortDescription>This rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
364 <longDescription>The Primitive To Object Conversion rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
365 </rule>
366 <rule>
367 <id>SocketRead</id>
368 <severity>Not Applicable</severity>
369 <score>-1.0</score>
370 <shortDescription>This rule requires events to be available from the following event types: 'Socket Read'.</shortDescription>
371 <longDescription>The Socket Read Peak Duration rule requires events to be available from the following event types: 'Socket Read'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
372 </rule>
373 <rule>
374 <id>SocketWrite</id>
375 <severity>Not Applicable</severity>
376 <score>-1.0</score>
377 <shortDescription>This rule requires events to be available from the following event types: 'Socket Write'.</shortDescription>
378 <longDescription>The Socket Write Peak Duration rule requires events to be available from the following event types: 'Socket Write'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
379 </rule>
380 <rule>
381 <id>StackdepthSetting</id>
382 <severity>OK</severity>
383 <score>0.0</score>
384 <shortDescription>No stack traces were truncated in this recording.</shortDescription>
385 <longDescription>No stack traces were truncated in this recording.</longDescription>
386 </rule>
387 <rule>
388 <id>StringDeduplication</id>
389 <severity>Not Applicable</severity>
390 <score>-1.0</score>
391 <shortDescription>Found no allocation events for the internal arrays in strings. Either the frame filter preference is incorrectly defined, or the stackTrace attribute is not enabled for the allocation events.</shortDescription>
392 <longDescription>Found no allocation events for the internal arrays in strings. Either the frame filter preference is incorrectly defined, or the stackTrace attribute is not enabled for the allocation events.</longDescription>
393 </rule>
394 <rule>
395 <id>SystemGc</id>
396 <severity>OK</severity>
397 <score>0.0</score>
398 <shortDescription>No garbage collections were caused by System.gc().</shortDescription>
399 <longDescription>No garbage collections were caused by System.gc().</longDescription>
400 </rule>
401 <rule>
402 <id>TlabAllocationRatio</id>
403 <severity>OK</severity>
404 <score>0.0</score>
405 <shortDescription>No object allocations outside of TLABs detected.</shortDescription>
406 <longDescription>No object allocations outside of TLABs detected.</longDescription>
407 </rule>
408 <rule>
409 <id>VMOperations</id>
410 <severity>OK</severity>
411 <score>0.75795475</score>
412 <shortDescription>No excessively long VM operations were found in this recording (the longest was 30.318 ms).</shortDescription>
413 <longDescription>No excessively long VM operations were found in this recording (the longest was 30.318 ms).</longDescription>
414 </rule>
415 <rule>
416 <id>biasedLockingRevocation</id>
417 <severity>Not Applicable</severity>
418 <score>-1.0</score>
419 <shortDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.</shortDescription>
420 <longDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.<p>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>
421 </rule>
422 <rule>
423 <id>biasedLockingRevocationPause</id>
424 <severity>OK</severity>
425 <score>0.0</score>
426 <shortDescription>No revocation of biased locks found.</shortDescription>
427 <longDescription>No revocation of biased locks found.</longDescription>
428 </rule>
429 </report>
430 <report>
431 <file>allocation_10s_fixed.jfr</file>
432 <rule>
433 <id>Allocations.class</id>
434 <severity>OK</severity>
435 <score>0.06321740358971492</score>
436 <shortDescription>The most allocated class is likely 'java.util.HashMap$ValueIterator'. This is the most common allocation path for that class: <ul><li>HashMap$Values.iterator() (100 %)</li><li>Allocator.go()</li><li>Allocator.main(String[])</li></ul></shortDescription>
437 <longDescription>The most allocated class is likely 'java.util.HashMap$ValueIterator'. This is the most common allocation path for that class: <ul><li>HashMap$Values.iterator() (100 %)</li><li>Allocator.go()</li><li>Allocator.main(String[])</li></ul><p>Frequently allocated classes are likely good places to start when trying to reduce garbage collections. Look at the aggregated stack traces of the most commonly allocated classes to see if many instances are created along the same call path. Try to reduce the number of instances created by invoking the most commonly taken paths less.</longDescription>
438 </rule>
439 <rule>
440 <id>Allocations.thread</id>
441 <severity>OK</severity>
442 <score>0.06321740358971492</score>
443 <shortDescription>The thread performing the most allocation is likely 'main'. This is the most common allocation path for that class: <ul><li>HashMap$Values.iterator() (100 %)</li><li>Allocator.go()</li><li>Allocator.main(String[])</li></ul></shortDescription>
444 <longDescription>The thread performing the most allocation is likely 'main'. This is the most common allocation path for that class: <ul><li>HashMap$Values.iterator() (100 %)</li><li>Allocator.go()</li><li>Allocator.main(String[])</li></ul><p>Many allocations performed by the same thread might indicate a problem in a multi-threaded program. Look at the aggregated stack traces for the thread with the highest allocation rate. See if the allocation rate can be brought down, or balanced among the active threads.</longDescription>
445 </rule>
446 <rule>
447 <id>ApplicationHalts</id>
448 <severity>OK</severity>
449 <score>0.15440711111111113</score>
450 <shortDescription>Application efficiency was not highly affected by halts.</shortDescription>
451 <longDescription>Application efficiency was not highly affected by halts.<p>The highest ratio between application halts and execution time was 0.031 % during 1 min starting at 4/26/18 12:12:46 PM. 100 % of the halts during the timespan were because of other reasons than GCs.<p>The total halts ratio during the entire recording was 0.187 %. 100 % of the total halts were because of other reasons than GCs.</longDescription>
452 </rule>
453 <rule>
454 <id>BufferLost</id>
455 <severity>OK</severity>
456 <score>0.0</score>
457 <shortDescription>No Flight Recorder buffers were lost during the recording.</shortDescription>
458 <longDescription>No Flight Recorder buffers were lost during the recording.</longDescription>
459 </rule>
460 <rule>
461 <id>BytecodeVerification</id>
462 <severity>OK</severity>
463 <score>0.0</score>
464 <shortDescription>The application was running with bytecode verification enabled.</shortDescription>
465 <longDescription>The application was running with bytecode verification enabled.</longDescription>
466 </rule>
467 <rule>
468 <id>ClassLeak</id>
469 <severity>Not Applicable</severity>
470 <score>-1.0</score>
471 <shortDescription>This rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.</shortDescription>
472 <longDescription>The Class Leak rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
473 </rule>
474 <rule>
475 <id>ClassLoading</id>
476 <severity>Not Applicable</severity>
477 <score>-1.0</score>
478 <shortDescription>This rule requires that the following event types are enabled: 'Class Load'.</shortDescription>
479 <longDescription>The Class Loading Pressure rule requires that the following event types are enabled: 'Class Load'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
480 </rule>
481 <rule>
482 <id>CodeCache</id>
483 <severity>OK</severity>
484 <score>21.808180522170357</score>
485 <shortDescription>No problems with the code cache were detected in the recording.</shortDescription>
486 <longDescription>No problems with the code cache were detected in the recording.</longDescription>
487 </rule>
488 <rule>
489 <id>CompareCpu</id>
490 <severity>OK</severity>
491 <score>8.569645731768105</score>
492 <shortDescription>An average CPU load of 7 % was caused by other processes during 1.212 s starting at 4/26/18 12:12:47 PM.</shortDescription>
493 <longDescription>An average CPU load of 7 % was caused by other processes during 1.212 s starting at 4/26/18 12:12:47 PM.</longDescription>
494 </rule>
495 <rule>
496 <id>CompressedOops</id>
497 <severity>OK</severity>
498 <score>0.0</score>
499 <shortDescription>The settings for Compressed Oops were OK.</shortDescription>
500 <longDescription>The settings for Compressed Oops were OK.</longDescription>
501 </rule>
502 <rule>
503 <id>ContextSwitch</id>
504 <severity>Not Applicable</severity>
505 <score>-1.0</score>
506 <shortDescription>This rule requires events to be available from the following event types: 'Thread Context Switch Rate'.</shortDescription>
507 <longDescription>The Context Switches rule requires events to be available from the following event types: 'Thread Context Switch Rate'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
508 </rule>
509 <rule>
510 <id>DMSIncident</id>
511 <severity>Not Applicable</severity>
512 <score>-1.0</score>
513 <shortDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.</shortDescription>
514 <longDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.<p>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>
515 </rule>
516 <rule>
517 <id>DebugNonSafepoints</id>
518 <severity>OK</severity>
519 <score>0.0</score>
520 <shortDescription>DebugNonSafepoints was implicitly enabled in the JVM version used to create this recording.</shortDescription>
521 <longDescription>DebugNonSafepoints was implicitly enabled in the JVM version used to create this recording.</longDescription>
522 </rule>
523 <rule>
524 <id>DiscouragedVmOptions</id>
525 <severity>OK</severity>
526 <score>0.0</score>
527 <shortDescription>No problems were found with the VM options.</shortDescription>
528 <longDescription>No problems were found with the VM options.</longDescription>
529 </rule>
530 <rule>
531 <id>DumpReason</id>
532 <severity>OK</severity>
533 <score>0.0</score>
534 <shortDescription>This recording was not dumped for an exceptional reason.</shortDescription>
535 <longDescription>This recording was not dumped for an exceptional reason.</longDescription>
536 </rule>
537 <rule>
538 <id>DuplicateFlags</id>
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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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'.<p>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).<p>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.<p>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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
585 </rule>
586 <rule>
587 <id>FlightRecordingSupport</id>
588 <severity>OK</severity>
589 <score>0.0</score>
590 <shortDescription>The JVM version used for this recording has full Flight Recorder support.</shortDescription>
591 <longDescription>The JVM version used for this recording has full Flight Recorder support.</longDescription>
592 </rule>
593 <rule>
594 <id>GcFreedRatio</id>
595 <severity>OK</severity>
596 <score>0.0</score>
597 <shortDescription>Only 0 heap summary events were found, this rule requires at least 10 events to be able to calculate a relevant result. This likely means that only a few garbage collections occurred during the recording. Having few garbage collections is generally a good sign.</shortDescription>
598 <longDescription>Only 0 heap summary events were found, this rule requires at least 10 events to be able to calculate a relevant result. This likely means that only a few garbage collections occurred during the recording. Having few garbage collections is generally a good sign.</longDescription>
599 </rule>
600 <rule>
601 <id>GcLocker</id>
602 <severity>OK</severity>
603 <score>0.0</score>
604 <shortDescription>The GC Locker did not cause any garbage collections.</shortDescription>
605 <longDescription>The GC Locker did not cause any garbage collections.</longDescription>
606 </rule>
607 <rule>
608 <id>GcOptions</id>
609 <severity>OK</severity>
610 <score>0.0</score>
611 <shortDescription>No problems were found with the GC configuration.</shortDescription>
612 <longDescription>No problems were found with the GC configuration.</longDescription>
613 </rule>
614 <rule>
615 <id>GcPauseRatio</id>
616 <severity>OK</severity>
617 <score>0.0</score>
618 <shortDescription>Application efficiency was not highly affected by GC pauses.</shortDescription>
619 <longDescription>Application efficiency was not highly affected by GC pauses.<p>The highest ratio between garbage collection pauses and execution time was 0 % during 1 min starting at 4/26/18 12:12:46 PM. The garbage collection pause ratio of the entire recording was 0 %.</longDescription>
620 </rule>
621 <rule>
622 <id>GcStall</id>
623 <severity>Not Applicable</severity>
624 <score>-1.0</score>
625 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
626 <longDescription>The GC Stall rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
627 </rule>
628 <rule>
629 <id>HeapContent</id>
630 <severity>Not Applicable</severity>
631 <score>-1.0</score>
632 <shortDescription>This rule requires that the following event types are enabled: 'Object Count'.</shortDescription>
633 <longDescription>The Heap Content rule requires that the following event types are enabled: 'Object Count'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
634 </rule>
635 <rule>
636 <id>HeapInspectionGc</id>
637 <severity>Not Applicable</severity>
638 <score>-1.0</score>
639 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
640 <longDescription>The GCs Caused by Heap Inspection rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
641 </rule>
642 <rule>
643 <id>HighGc</id>
644 <severity>OK</severity>
645 <score>0.0</score>
646 <shortDescription>The runtime did not spend much time performing garbage collections.</shortDescription>
647 <longDescription>The runtime did not spend much time performing garbage collections.</longDescription>
648 </rule>
649 <rule>
650 <id>HighJvmCpu</id>
651 <severity>OK</severity>
652 <score>1.193150385433165</score>
653 <shortDescription>The JVM does not seem to cause a lot of CPU load.</shortDescription>
654 <longDescription>The JVM does not seem to cause a lot of CPU load.</longDescription>
655 </rule>
656 <rule>
657 <id>IncreasingLiveSet</id>
658 <severity>Not Applicable</severity>
659 <score>-1.0</score>
660 <shortDescription>Too few events to calculate the result.</shortDescription>
661 <longDescription>Too few events to calculate the result.</longDescription>
662 </rule>
663 <rule>
664 <id>IncreasingMetaSpaceLiveSet</id>
665 <severity>OK</severity>
666 <score>0.0</score>
667 <shortDescription>The class data does not seem to increase during the recording.</shortDescription>
668 <longDescription>The class data does not seem to increase during the recording.</longDescription>
669 </rule>
670 <rule>
671 <id>JavaBlocking</id>
672 <severity>Not Applicable</severity>
673 <score>-1.0</score>
674 <shortDescription>This rule requires events to be available from the following event types: 'Java Monitor Blocked'.</shortDescription>
675 <longDescription>The Java Blocking rule requires events to be available from the following event types: 'Java Monitor Blocked'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
676 </rule>
677 <rule>
678 <id>LongGcPause</id>
679 <severity>OK</severity>
680 <score>0.0</score>
681 <shortDescription>The application did not cause any long GC pause times.</shortDescription>
682 <longDescription>The application did not cause any long GC pause times.</longDescription>
683 </rule>
684 <rule>
685 <id>LowOnPhysicalMemory</id>
686 <severity>OK</severity>
687 <score>0.0</score>
688 <shortDescription>The system did not run low on physical memory during this recording.</shortDescription>
689 <longDescription>The system did not run low on physical memory during this recording.</longDescription>
690 </rule>
691 <rule>
692 <id>ManagementAgent</id>
693 <severity>Not Applicable</severity>
694 <score>-1.0</score>
695 <shortDescription>This rule requires that the following event types are enabled: 'Initial System Property'.</shortDescription>
696 <longDescription>The Discouraged Management Agent Settings rule requires that the following event types are enabled: 'Initial System Property'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
697 </rule>
698 <rule>
699 <id>ManyRunningProcesses</id>
700 <severity>Not Applicable</severity>
701 <score>-1.0</score>
702 <shortDescription>This rule requires that the following event types are enabled: 'System Process'.</shortDescription>
703 <longDescription>The Competing Processes rule requires that the following event types are enabled: 'System Process'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
704 </rule>
705 <rule>
706 <id>MetaspaceOom</id>
707 <severity>OK</severity>
708 <score>0.0</score>
709 <shortDescription>The metaspace was not exhausted during this recording.</shortDescription>
710 <longDescription>The metaspace was not exhausted during this recording.</longDescription>
711 </rule>
712 <rule>
713 <id>MethodProfiling</id>
714 <severity>OK</severity>
715 <score>0.0</score>
716 <shortDescription>No methods where optimization would be particularly efficient could be detected.</shortDescription>
717 <longDescription>No methods where optimization would be particularly efficient could be detected.</longDescription>
718 </rule>
719 <rule>
720 <id>Options</id>
721 <severity>OK</severity>
722 <score>0.0</score>
723 <shortDescription>No undocumented, deprecated or non-recommended option flags were detected.</shortDescription>
724 <longDescription>No undocumented, deprecated or non-recommended option flags were detected.</longDescription>
725 </rule>
726 <rule>
727 <id>OverAggressiveRecordingSetting</id>
728 <severity>Not Applicable</severity>
729 <score>-1.0</score>
730 <shortDescription>This rule requires that the following event types are enabled: 'Initial System Property'.</shortDescription>
731 <longDescription>The Discouraged Recording Settings rule requires that the following event types are enabled: 'Initial System Property'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
732 </rule>
733 <rule>
734 <id>PasswordsInArguments</id>
735 <severity>OK</severity>
736 <score>0.0</score>
737 <shortDescription>The recording does not seem to contain passwords in the application arguments.</shortDescription>
738 <longDescription>The recording does not seem to contain passwords in the application arguments.</longDescription>
739 </rule>
740 <rule>
741 <id>PasswordsInEnvironment</id>
742 <severity>Not Applicable</severity>
743 <score>-1.0</score>
744 <shortDescription>This rule requires that the following event types are enabled: 'Initial Environment Variable'.</shortDescription>
745 <longDescription>The Passwords in Environment Variables rule requires that the following event types are enabled: 'Initial Environment Variable'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
746 </rule>
747 <rule>
748 <id>PasswordsInSystemProperties</id>
749 <severity>Not Applicable</severity>
750 <score>-1.0</score>
751 <shortDescription>This rule requires that the following event types are enabled: 'Initial System Property'.</shortDescription>
752 <longDescription>The Passwords in System Properties rule requires that the following event types are enabled: 'Initial System Property'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
753 </rule>
754 <rule>
755 <id>PrimitiveToObjectConversion</id>
756 <severity>Not Applicable</severity>
757 <score>-1.0</score>
758 <shortDescription>This rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
759 <longDescription>The Primitive To Object Conversion rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
760 </rule>
761 <rule>
762 <id>SocketRead</id>
763 <severity>Not Applicable</severity>
764 <score>-1.0</score>
765 <shortDescription>This rule requires events to be available from the following event types: 'Socket Read'.</shortDescription>
766 <longDescription>The Socket Read Peak Duration rule requires events to be available from the following event types: 'Socket Read'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
767 </rule>
768 <rule>
769 <id>SocketWrite</id>
770 <severity>Not Applicable</severity>
771 <score>-1.0</score>
772 <shortDescription>This rule requires events to be available from the following event types: 'Socket Write'.</shortDescription>
773 <longDescription>The Socket Write Peak Duration rule requires events to be available from the following event types: 'Socket Write'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
774 </rule>
775 <rule>
776 <id>StackdepthSetting</id>
777 <severity>OK</severity>
778 <score>0.0</score>
779 <shortDescription>No stack traces were truncated in this recording.</shortDescription>
780 <longDescription>No stack traces were truncated in this recording.</longDescription>
781 </rule>
782 <rule>
783 <id>StringDeduplication</id>
784 <severity>Not Applicable</severity>
785 <score>-1.0</score>
786 <shortDescription>This rule requires events to be available from the following event types: 'Heap Summary'.</shortDescription>
787 <longDescription>The String Deduplication rule requires events to be available from the following event types: 'Heap Summary'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
788 </rule>
789 <rule>
790 <id>SystemGc</id>
791 <severity>Not Applicable</severity>
792 <score>-1.0</score>
793 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
794 <longDescription>The GCs Caused by System.gc() rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
795 </rule>
796 <rule>
797 <id>TlabAllocationRatio</id>
798 <severity>OK</severity>
799 <score>0.0</score>
800 <shortDescription>No object allocations outside of TLABs detected.</shortDescription>
801 <longDescription>No object allocations outside of TLABs detected.</longDescription>
802 </rule>
803 <rule>
804 <id>VMOperations</id>
805 <severity>OK</severity>
806 <score>0.44893575</score>
807 <shortDescription>No excessively long VM operations were found in this recording (the longest was 17.957 ms).</shortDescription>
808 <longDescription>No excessively long VM operations were found in this recording (the longest was 17.957 ms).</longDescription>
809 </rule>
810 <rule>
811 <id>biasedLockingRevocation</id>
812 <severity>Not Applicable</severity>
813 <score>-1.0</score>
814 <shortDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.</shortDescription>
815 <longDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.<p>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>
816 </rule>
817 <rule>
818 <id>biasedLockingRevocationPause</id>
819 <severity>OK</severity>
820 <score>0.0</score>
821 <shortDescription>No revocation of biased locks found.</shortDescription>
822 <longDescription>No revocation of biased locks found.</longDescription>
823 </rule>
824 </report>
825 <report>
826 <file>crash_jdk9.jfr</file>
827 <rule>
828 <id>Allocations.class</id>
829 <severity>Not Applicable</severity>
830 <score>-1.0</score>
831 <shortDescription>This rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
832 <longDescription>The Allocated Classes rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
833 </rule>
834 <rule>
835 <id>Allocations.thread</id>
836 <severity>Not Applicable</severity>
837 <score>-1.0</score>
838 <shortDescription>This rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
839 <longDescription>The Threads Allocating rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
840 </rule>
841 <rule>
842 <id>ApplicationHalts</id>
843 <severity>OK</severity>
844 <score>0.0</score>
845 <shortDescription>Application efficiency was not highly affected by halts.</shortDescription>
846 <longDescription>Application efficiency was not highly affected by halts.<p>The highest ratio between application halts and execution time was 0 % during 1 min starting at 4/24/18 10:16:27 AM. 0 % of the halts during the timespan were because of other reasons than GCs.<p>The total halts ratio during the entire recording was 0 %. 0 % of the total halts were because of other reasons than GCs.</longDescription>
847 </rule>
848 <rule>
849 <id>BufferLost</id>
850 <severity>OK</severity>
851 <score>0.0</score>
852 <shortDescription>No Flight Recorder buffers were lost during the recording.</shortDescription>
853 <longDescription>No Flight Recorder buffers were lost during the recording.</longDescription>
854 </rule>
855 <rule>
856 <id>BytecodeVerification</id>
857 <severity>OK</severity>
858 <score>0.0</score>
859 <shortDescription>The application was running with bytecode verification enabled.</shortDescription>
860 <longDescription>The application was running with bytecode verification enabled.</longDescription>
861 </rule>
862 <rule>
863 <id>ClassLeak</id>
864 <severity>Not Applicable</severity>
865 <score>-1.0</score>
866 <shortDescription>This rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.</shortDescription>
867 <longDescription>The Class Leak rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
868 </rule>
869 <rule>
870 <id>ClassLoading</id>
871 <severity>Not Applicable</severity>
872 <score>-1.0</score>
873 <shortDescription>This rule requires that the following event types are enabled: 'Class Load'.</shortDescription>
874 <longDescription>The Class Loading Pressure rule requires that the following event types are enabled: 'Class Load'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
875 </rule>
876 <rule>
877 <id>CodeCache</id>
878 <severity>OK</severity>
879 <score>21.686110914128236</score>
880 <shortDescription>No problems with the code cache were detected in the recording.</shortDescription>
881 <longDescription>No problems with the code cache were detected in the recording.</longDescription>
882 </rule>
883 <rule>
884 <id>CompareCpu</id>
885 <severity>Not Applicable</severity>
886 <score>-1.0</score>
887 <shortDescription>This rule requires events to be available from the following event types: 'CPU Load'.</shortDescription>
888 <longDescription>The Competing CPU Usage rule requires events to be available from the following event types: 'CPU Load'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
889 </rule>
890 <rule>
891 <id>CompressedOops</id>
892 <severity>OK</severity>
893 <score>0.0</score>
894 <shortDescription>The settings for Compressed Oops were OK.</shortDescription>
895 <longDescription>The settings for Compressed Oops were OK.</longDescription>
896 </rule>
897 <rule>
898 <id>ContextSwitch</id>
899 <severity>Not Applicable</severity>
900 <score>-1.0</score>
901 <shortDescription>This rule requires events to be available from the following event types: 'Thread Context Switch Rate'.</shortDescription>
902 <longDescription>The Context Switches rule requires events to be available from the following event types: 'Thread Context Switch Rate'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
903 </rule>
904 <rule>
905 <id>DMSIncident</id>
906 <severity>Not Applicable</severity>
907 <score>-1.0</score>
908 <shortDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.</shortDescription>
909 <longDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.<p>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>
910 </rule>
911 <rule>
912 <id>DebugNonSafepoints</id>
913 <severity>OK</severity>
914 <score>0.0</score>
915 <shortDescription>DebugNonSafepoints was implicitly enabled in the JVM version used to create this recording.</shortDescription>
916 <longDescription>DebugNonSafepoints was implicitly enabled in the JVM version used to create this recording.</longDescription>
917 </rule>
918 <rule>
919 <id>DiscouragedVmOptions</id>
920 <severity>OK</severity>
921 <score>0.0</score>
922 <shortDescription>No problems were found with the VM options.</shortDescription>
923 <longDescription>No problems were found with the VM options.</longDescription>
924 </rule>
925 <rule>
926 <id>DumpReason</id>
927 <severity>Warning</severity>
928 <score>100.0</score>
929 <shortDescription>This recording was dumped for an exceptional reason.</shortDescription>
930 <longDescription>Recording was dumped due to a JVM crash. Some events are likely missing from the end of the recording.</longDescription>
931 </rule>
932 <rule>
933 <id>DuplicateFlags</id>
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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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'.<p>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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
980 </rule>
981 <rule>
982 <id>FlightRecordingSupport</id>
983 <severity>OK</severity>
984 <score>0.0</score>
985 <shortDescription>The JVM version used for this recording has full Flight Recorder support.</shortDescription>
986 <longDescription>The JVM version used for this recording has full Flight Recorder support.</longDescription>
987 </rule>
988 <rule>
989 <id>GcFreedRatio</id>
990 <severity>OK</severity>
991 <score>0.0</score>
992 <shortDescription>Only 0 heap summary events were found, this rule requires at least 10 events to be able to calculate a relevant result. This likely means that only a few garbage collections occurred during the recording. Having few garbage collections is generally a good sign.</shortDescription>
993 <longDescription>Only 0 heap summary events were found, this rule requires at least 10 events to be able to calculate a relevant result. This likely means that only a few garbage collections occurred during the recording. Having few garbage collections is generally a good sign.</longDescription>
994 </rule>
995 <rule>
996 <id>GcLocker</id>
997 <severity>OK</severity>
998 <score>0.0</score>
999 <shortDescription>The GC Locker did not cause any garbage collections.</shortDescription>
1000 <longDescription>The GC Locker did not cause any garbage collections.</longDescription>
1001 </rule>
1002 <rule>
1003 <id>GcOptions</id>
1004 <severity>OK</severity>
1005 <score>0.0</score>
1006 <shortDescription>No problems were found with the GC configuration.</shortDescription>
1007 <longDescription>No problems were found with the GC configuration.</longDescription>
1008 </rule>
1009 <rule>
1010 <id>GcPauseRatio</id>
1011 <severity>OK</severity>
1012 <score>0.0</score>
1013 <shortDescription>Application efficiency was not highly affected by GC pauses.</shortDescription>
1014 <longDescription>Application efficiency was not highly affected by GC pauses.<p>The highest ratio between garbage collection pauses and execution time was 0 % during 1 min starting at 4/24/18 10:16:27 AM. The garbage collection pause ratio of the entire recording was 0 %.</longDescription>
1015 </rule>
1016 <rule>
1017 <id>GcStall</id>
1018 <severity>Not Applicable</severity>
1019 <score>-1.0</score>
1020 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
1021 <longDescription>The GC Stall rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1022 </rule>
1023 <rule>
1024 <id>HeapContent</id>
1025 <severity>Not Applicable</severity>
1026 <score>-1.0</score>
1027 <shortDescription>This rule requires that the following event types are enabled: 'Object Count'.</shortDescription>
1028 <longDescription>The Heap Content rule requires that the following event types are enabled: 'Object Count'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1029 </rule>
1030 <rule>
1031 <id>HeapInspectionGc</id>
1032 <severity>Not Applicable</severity>
1033 <score>-1.0</score>
1034 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
1035 <longDescription>The GCs Caused by Heap Inspection rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1036 </rule>
1037 <rule>
1038 <id>HighGc</id>
1039 <severity>OK</severity>
1040 <score>0.0</score>
1041 <shortDescription>The runtime did not spend much time performing garbage collections.</shortDescription>
1042 <longDescription>The runtime did not spend much time performing garbage collections.</longDescription>
1043 </rule>
1044 <rule>
1045 <id>HighJvmCpu</id>
1046 <severity>Not Applicable</severity>
1047 <score>-1.0</score>
1048 <shortDescription>This rule requires events to be available from the following event types: 'CPU Load'.</shortDescription>
1049 <longDescription>The High JVM CPU Load rule requires events to be available from the following event types: 'CPU Load'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1050 </rule>
1051 <rule>
1052 <id>IncreasingLiveSet</id>
1053 <severity>Not Applicable</severity>
1054 <score>-1.0</score>
1055 <shortDescription>Too few events to calculate the result.</shortDescription>
1056 <longDescription>Too few events to calculate the result.</longDescription>
1057 </rule>
1058 <rule>
1059 <id>IncreasingMetaSpaceLiveSet</id>
1060 <severity>OK</severity>
1061 <score>0.0</score>
1062 <shortDescription>The class data does not seem to increase during the recording.</shortDescription>
1063 <longDescription>The class data does not seem to increase during the recording.</longDescription>
1064 </rule>
1065 <rule>
1066 <id>JavaBlocking</id>
1067 <severity>Not Applicable</severity>
1068 <score>-1.0</score>
1069 <shortDescription>This rule requires events to be available from the following event types: 'Java Monitor Blocked'.</shortDescription>
1070 <longDescription>The Java Blocking rule requires events to be available from the following event types: 'Java Monitor Blocked'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1071 </rule>
1072 <rule>
1073 <id>LongGcPause</id>
1074 <severity>OK</severity>
1075 <score>0.0</score>
1076 <shortDescription>The application did not cause any long GC pause times.</shortDescription>
1077 <longDescription>The application did not cause any long GC pause times.</longDescription>
1078 </rule>
1079 <rule>
1080 <id>LowOnPhysicalMemory</id>
1081 <severity>Information</severity>
1082 <score>51.06889156143796</score>
1083 <shortDescription>The maximum amount of used memory was 88.9 % of the physical memory available.</shortDescription>
1084 <longDescription>The maximum amount of used memory was 28.4 GiB. This is 88.9 % of the 31.9 GiB of physical memory available. Having little free memory may lead to swapping, which is very expensive. To avoid this, either decrease the memory usage or increase the amount of available memory.</longDescription>
1085 </rule>
1086 <rule>
1087 <id>ManagementAgent</id>
1088 <severity>Not Applicable</severity>
1089 <score>-1.0</score>
1090 <shortDescription>This rule requires that the following event types are enabled: 'Initial System Property'.</shortDescription>
1091 <longDescription>The Discouraged Management Agent Settings rule requires that the following event types are enabled: 'Initial System Property'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1092 </rule>
1093 <rule>
1094 <id>ManyRunningProcesses</id>
1095 <severity>Not Applicable</severity>
1096 <score>-1.0</score>
1097 <shortDescription>This rule requires that the following event types are enabled: 'System Process'.</shortDescription>
1098 <longDescription>The Competing Processes rule requires that the following event types are enabled: 'System Process'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1099 </rule>
1100 <rule>
1101 <id>MetaspaceOom</id>
1102 <severity>OK</severity>
1103 <score>0.0</score>
1104 <shortDescription>The metaspace was not exhausted during this recording.</shortDescription>
1105 <longDescription>The metaspace was not exhausted during this recording.</longDescription>
1106 </rule>
1107 <rule>
1108 <id>MethodProfiling</id>
1109 <severity>Not Applicable</severity>
1110 <score>-1.0</score>
1111 <shortDescription>This rule requires events to be available from the following event types: 'Method Profiling Sample', 'Recording Setting'.</shortDescription>
1112 <longDescription>The Method Profiling rule requires events to be available from the following event types: 'Method Profiling Sample', 'Recording Setting'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1113 </rule>
1114 <rule>
1115 <id>Options</id>
1116 <severity>OK</severity>
1117 <score>0.0</score>
1118 <shortDescription>No undocumented, deprecated or non-recommended option flags were detected.</shortDescription>
1119 <longDescription>No undocumented, deprecated or non-recommended option flags were detected.</longDescription>
1120 </rule>
1121 <rule>
1122 <id>OverAggressiveRecordingSetting</id>
1123 <severity>Not Applicable</severity>
1124 <score>-1.0</score>
1125 <shortDescription>This rule requires that the following event types are enabled: 'Initial System Property'.</shortDescription>
1126 <longDescription>The Discouraged Recording Settings rule requires that the following event types are enabled: 'Initial System Property'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1127 </rule>
1128 <rule>
1129 <id>PasswordsInArguments</id>
1130 <severity>OK</severity>
1131 <score>0.0</score>
1132 <shortDescription>The recording does not seem to contain passwords in the application arguments.</shortDescription>
1133 <longDescription>The recording does not seem to contain passwords in the application arguments.</longDescription>
1134 </rule>
1135 <rule>
1136 <id>PasswordsInEnvironment</id>
1137 <severity>Not Applicable</severity>
1138 <score>-1.0</score>
1139 <shortDescription>This rule requires that the following event types are enabled: 'Initial Environment Variable'.</shortDescription>
1140 <longDescription>The Passwords in Environment Variables rule requires that the following event types are enabled: 'Initial Environment Variable'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1141 </rule>
1142 <rule>
1143 <id>PasswordsInSystemProperties</id>
1144 <severity>Not Applicable</severity>
1145 <score>-1.0</score>
1146 <shortDescription>This rule requires that the following event types are enabled: 'Initial System Property'.</shortDescription>
1147 <longDescription>The Passwords in System Properties rule requires that the following event types are enabled: 'Initial System Property'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1148 </rule>
1149 <rule>
1150 <id>PrimitiveToObjectConversion</id>
1151 <severity>Not Applicable</severity>
1152 <score>-1.0</score>
1153 <shortDescription>This rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
1154 <longDescription>The Primitive To Object Conversion rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1155 </rule>
1156 <rule>
1157 <id>SocketRead</id>
1158 <severity>Not Applicable</severity>
1159 <score>-1.0</score>
1160 <shortDescription>This rule requires events to be available from the following event types: 'Socket Read'.</shortDescription>
1161 <longDescription>The Socket Read Peak Duration rule requires events to be available from the following event types: 'Socket Read'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1162 </rule>
1163 <rule>
1164 <id>SocketWrite</id>
1165 <severity>Not Applicable</severity>
1166 <score>-1.0</score>
1167 <shortDescription>This rule requires events to be available from the following event types: 'Socket Write'.</shortDescription>
1168 <longDescription>The Socket Write Peak Duration rule requires events to be available from the following event types: 'Socket Write'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1169 </rule>
1170 <rule>
1171 <id>StackdepthSetting</id>
1172 <severity>OK</severity>
1173 <score>0.0</score>
1174 <shortDescription>No stack traces were truncated in this recording.</shortDescription>
1175 <longDescription>No stack traces were truncated in this recording.</longDescription>
1176 </rule>
1177 <rule>
1178 <id>StringDeduplication</id>
1179 <severity>Not Applicable</severity>
1180 <score>-1.0</score>
1181 <shortDescription>This rule requires events to be available from the following event types: 'Heap Summary'.</shortDescription>
1182 <longDescription>The String Deduplication rule requires events to be available from the following event types: 'Heap Summary'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1183 </rule>
1184 <rule>
1185 <id>SystemGc</id>
1186 <severity>Not Applicable</severity>
1187 <score>-1.0</score>
1188 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
1189 <longDescription>The GCs Caused by System.gc() rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1190 </rule>
1191 <rule>
1192 <id>TlabAllocationRatio</id>
1193 <severity>Not Applicable</severity>
1194 <score>-1.0</score>
1195 <shortDescription>This rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
1196 <longDescription>The TLAB Allocation Ratio rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1197 </rule>
1198 <rule>
1199 <id>VMOperations</id>
1200 <severity>OK</severity>
1201 <score>0.0</score>
1202 <shortDescription>No excessively long VM operations were found in this recording (the longest was 0 s).</shortDescription>
1203 <longDescription>No excessively long VM operations were found in this recording (the longest was 0 s).</longDescription>
1204 </rule>
1205 <rule>
1206 <id>biasedLockingRevocation</id>
1207 <severity>Not Applicable</severity>
1208 <score>-1.0</score>
1209 <shortDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.</shortDescription>
1210 <longDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.<p>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>
1211 </rule>
1212 <rule>
1213 <id>biasedLockingRevocationPause</id>
1214 <severity>OK</severity>
1215 <score>0.0</score>
1216 <shortDescription>No revocation of biased locks found.</shortDescription>
1217 <longDescription>No revocation of biased locks found.</longDescription>
1218 </rule>
1219 </report>
1220 <report>
1221 <file>flight_recording_hidden.jfr</file>
1222 <rule>
1223 <id>Allocations.class</id>
1224 <severity>OK</severity>
1225 <score>0.09287686767432358</score>
1226 <shortDescription>The most allocated class is likely 'byte[]'. This is the most common allocation path for that class: <ul><li>ByteArrayOutputStream.&lt;init&gt;(int) (50 %)</li><li>ByteArrayOutputStream.&lt;init&gt;()</li><li>JdpPacketWriter.&lt;init&gt;()</li><li>JdpJmxPacket.getPacketData()</li><li>JdpBroadcaster.sendPacket(JdpPacket)</li><li>JdpController$JDPControllerRunner.run()</li></ul></shortDescription>
1227 <longDescription>The most allocated class is likely 'byte[]'. This is the most common allocation path for that class: <ul><li>ByteArrayOutputStream.&lt;init&gt;(int) (50 %)</li><li>ByteArrayOutputStream.&lt;init&gt;()</li><li>JdpPacketWriter.&lt;init&gt;()</li><li>JdpJmxPacket.getPacketData()</li><li>JdpBroadcaster.sendPacket(JdpPacket)</li><li>JdpController$JDPControllerRunner.run()</li></ul><p>Frequently allocated classes are likely good places to start when trying to reduce garbage collections. Look at the aggregated stack traces of the most commonly allocated classes to see if many instances are created along the same call path. Try to reduce the number of instances created by invoking the most commonly taken paths less.</longDescription>
1228 </rule>
1229 <rule>
1230 <id>Allocations.thread</id>
1231 <severity>OK</severity>
1232 <score>0.1274345677812541</score>
1233 <shortDescription>The thread performing the most allocation is likely 'AWT-EventQueue-0'. This is the most common allocation path for that class: <ul><li>EventQueue.dispatchEvent(AWTEvent) (60 %)</li><li>EventDispatchThread.pumpOneEventForFilters(int)</li><li>EventDispatchThread.pumpEventsForFilter(int, Conditional, EventFilter)</li><li>EventDispatchThread.pumpEventsForHierarchy(int, Conditional, Component)</li><li>EventDispatchThread.pumpEvents(int, Conditional)</li><li>EventDispatchThread.pumpEvents(Conditional)</li></ul></shortDescription>
1234 <longDescription>The thread performing the most allocation is likely 'AWT-EventQueue-0'. This is the most common allocation path for that class: <ul><li>EventQueue.dispatchEvent(AWTEvent) (60 %)</li><li>EventDispatchThread.pumpOneEventForFilters(int)</li><li>EventDispatchThread.pumpEventsForFilter(int, Conditional, EventFilter)</li><li>EventDispatchThread.pumpEventsForHierarchy(int, Conditional, Component)</li><li>EventDispatchThread.pumpEvents(int, Conditional)</li><li>EventDispatchThread.pumpEvents(Conditional)</li></ul><p>Many allocations performed by the same thread might indicate a problem in a multi-threaded program. Look at the aggregated stack traces for the thread with the highest allocation rate. See if the allocation rate can be brought down, or balanced among the active threads.</longDescription>
1235 </rule>
1236 <rule>
1237 <id>ApplicationHalts</id>
1238 <severity>Not Applicable</severity>
1239 <score>-1.0</score>
1240 <shortDescription>This rule requires events to be available from the following event types: 'GC Phase Pause', 'VM Operation'.</shortDescription>
1241 <longDescription>The Application Halts rule requires events to be available from the following event types: 'GC Phase Pause', 'VM Operation'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1242 </rule>
1243 <rule>
1244 <id>BufferLost</id>
1245 <severity>OK</severity>
1246 <score>0.0</score>
1247 <shortDescription>No Flight Recorder buffers were lost during the recording.</shortDescription>
1248 <longDescription>No Flight Recorder buffers were lost during the recording.</longDescription>
1249 </rule>
1250 <rule>
1251 <id>BytecodeVerification</id>
1252 <severity>OK</severity>
1253 <score>0.0</score>
1254 <shortDescription>The application was running with bytecode verification enabled.</shortDescription>
1255 <longDescription>The application was running with bytecode verification enabled.</longDescription>
1256 </rule>
1257 <rule>
1258 <id>ClassLeak</id>
1259 <severity>Not Applicable</severity>
1260 <score>-1.0</score>
1261 <shortDescription>This rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.</shortDescription>
1262 <longDescription>The Class Leak rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1263 </rule>
1264 <rule>
1265 <id>ClassLoading</id>
1266 <severity>Not Applicable</severity>
1267 <score>-1.0</score>
1268 <shortDescription>This rule requires that the following event types are enabled: 'Class Load'.</shortDescription>
1269 <longDescription>The Class Loading Pressure rule requires that the following event types are enabled: 'Class Load'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1270 </rule>
1271 <rule>
1272 <id>CodeCache</id>
1273 <severity>Not Applicable</severity>
1274 <score>-1.0</score>
1275 <shortDescription>This rule requires events to be available from the following event types: 'Code Cache Configuration', 'Code Cache Full', 'Code Cache Statistics', 'JVM Information'.</shortDescription>
1276 <longDescription>The Code Cache rule requires events to be available from the following event types: 'Code Cache Configuration', 'Code Cache Full', 'Code Cache Statistics', 'JVM Information'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1277 </rule>
1278 <rule>
1279 <id>CompareCpu</id>
1280 <severity>Warning</severity>
1281 <score>91.8903586610899</score>
1282 <shortDescription>An average CPU load of 60 % was caused by other processes during 8.047 s starting at 4/25/18 11:38:36 AM.</shortDescription>
1283 <longDescription>An average CPU load of 60 % was caused by other processes during 8.047 s starting at 4/25/18 11:38:36 AM.<p>The application performance can be affected if there are other processes that use CPU or other resources on the same computer. To profile representatively or get higher throughput, shut down other resource intensive processes running on the machine.</longDescription>
1284 </rule>
1285 <rule>
1286 <id>CompressedOops</id>
1287 <severity>Not Applicable</severity>
1288 <score>-1.0</score>
1289 <shortDescription>This rule requires events to be available from the following event types: 'Boolean Flag', 'JVM Information', 'Unsigned Long Flag'.</shortDescription>
1290 <longDescription>The Compressed Oops rule requires events to be available from the following event types: 'Boolean Flag', 'JVM Information', 'Unsigned Long Flag'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1291 </rule>
1292 <rule>
1293 <id>ContextSwitch</id>
1294 <severity>OK</severity>
1295 <score>0.0</score>
1296 <shortDescription>The program did not context switch excessively during the recording.</shortDescription>
1297 <longDescription>The program did not context switch excessively during the recording.</longDescription>
1298 </rule>
1299 <rule>
1300 <id>DMSIncident</id>
1301 <severity>Not Applicable</severity>
1302 <score>-1.0</score>
1303 <shortDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.</shortDescription>
1304 <longDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.<p>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>
1305 </rule>
1306 <rule>
1307 <id>DebugNonSafepoints</id>
1308 <severity>Information</severity>
1309 <score>50.0</score>
1310 <shortDescription>DebugNonSafepoints was not enabled.</shortDescription>
1311 <longDescription>DebugNonSafepoints was not enabled.<p>If DebugNonSafepoints is not enabled, the method profiling data will be less accurate as threads that are not at safepoints will not be correctly sampled. Use the following JVM flags to enable this: '-XX:+UnlockDiagnosticVMOptions -XX:+DebugNonSafepoints'. There is a slight performance overhead when enabling these flags. For more information see <a href="http://openjdk.java.net/groups/hotspot/docs/RuntimeOverview.html#Thread%20Management|outline">HotSpot Runtime Overview/Thread Management</a>.</longDescription>
1312 </rule>
1313 <rule>
1314 <id>DiscouragedVmOptions</id>
1315 <severity>Not Applicable</severity>
1316 <score>-1.0</score>
1317 <shortDescription>This rule requires that the following event types are enabled: 'Boolean Flag'.</shortDescription>
1318 <longDescription>The Discouraged VM Options rule requires that the following event types are enabled: 'Boolean Flag'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1319 </rule>
1320 <rule>
1321 <id>DumpReason</id>
1322 <severity>OK</severity>
1323 <score>0.0</score>
1324 <shortDescription>This recording was not dumped for an exceptional reason.</shortDescription>
1325 <longDescription>This recording was not dumped for an exceptional reason.</longDescription>
1326 </rule>
1327 <rule>
1328 <id>DuplicateFlags</id>
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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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'.<p>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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1375 </rule>
1376 <rule>
1377 <id>FlightRecordingSupport</id>
1378 <severity>OK</severity>
1379 <score>0.0</score>
1380 <shortDescription>The JVM version used for this recording has full Flight Recorder support.</shortDescription>
1381 <longDescription>The JVM version used for this recording has full Flight Recorder support.</longDescription>
1382 </rule>
1383 <rule>
1384 <id>GcFreedRatio</id>
1385 <severity>Not Applicable</severity>
1386 <score>-1.0</score>
1387 <shortDescription>This rule requires that the following event types are enabled: 'Heap Summary'.</shortDescription>
1388 <longDescription>The GC Freed Ratio rule requires that the following event types are enabled: 'Heap Summary'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1389 </rule>
1390 <rule>
1391 <id>GcLocker</id>
1392 <severity>Not Applicable</severity>
1393 <score>-1.0</score>
1394 <shortDescription>This rule requires that the following event types are enabled: 'Garbage Collection'.</shortDescription>
1395 <longDescription>The GCs Caused by GC Locker rule requires that the following event types are enabled: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1396 </rule>
1397 <rule>
1398 <id>GcOptions</id>
1399 <severity>OK</severity>
1400 <score>0.0</score>
1401 <shortDescription>No problems were found with the GC configuration.</shortDescription>
1402 <longDescription>No problems were found with the GC configuration.</longDescription>
1403 </rule>
1404 <rule>
1405 <id>GcPauseRatio</id>
1406 <severity>Not Applicable</severity>
1407 <score>-1.0</score>
1408 <shortDescription>This rule requires that the following event types are enabled: 'GC Phase Pause'.</shortDescription>
1409 <longDescription>The GC Pauses rule requires that the following event types are enabled: 'GC Phase Pause'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1410 </rule>
1411 <rule>
1412 <id>GcStall</id>
1413 <severity>Not Applicable</severity>
1414 <score>-1.0</score>
1415 <shortDescription>This rule requires that the following event types are enabled: 'Garbage Collection'.</shortDescription>
1416 <longDescription>The GC Stall rule requires that the following event types are enabled: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1417 </rule>
1418 <rule>
1419 <id>HeapContent</id>
1420 <severity>Not Applicable</severity>
1421 <score>-1.0</score>
1422 <shortDescription>This rule requires that the following event types are enabled: 'Object Count'.</shortDescription>
1423 <longDescription>The Heap Content rule requires that the following event types are enabled: 'Object Count'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1424 </rule>
1425 <rule>
1426 <id>HeapInspectionGc</id>
1427 <severity>Not Applicable</severity>
1428 <score>-1.0</score>
1429 <shortDescription>This rule requires that the following event types are enabled: 'Garbage Collection'.</shortDescription>
1430 <longDescription>The GCs Caused by Heap Inspection rule requires that the following event types are enabled: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1431 </rule>
1432 <rule>
1433 <id>HighGc</id>
1434 <severity>Not Applicable</severity>
1435 <score>-1.0</score>
1436 <shortDescription>This rule requires that the following event types are enabled: 'GC Phase Pause'.</shortDescription>
1437 <longDescription>The GC Pressure rule requires that the following event types are enabled: 'GC Phase Pause'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1438 </rule>
1439 <rule>
1440 <id>HighJvmCpu</id>
1441 <severity>OK</severity>
1442 <score>0.8641130870553131</score>
1443 <shortDescription>The JVM does not seem to cause a lot of CPU load.</shortDescription>
1444 <longDescription>The JVM does not seem to cause a lot of CPU load.</longDescription>
1445 </rule>
1446 <rule>
1447 <id>IncreasingLiveSet</id>
1448 <severity>Not Applicable</severity>
1449 <score>-1.0</score>
1450 <shortDescription>This rule requires that the following event types are enabled: 'Heap Summary'.</shortDescription>
1451 <longDescription>The Heap Live Set Trend rule requires that the following event types are enabled: 'Heap Summary'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1452 </rule>
1453 <rule>
1454 <id>IncreasingMetaSpaceLiveSet</id>
1455 <severity>Not Applicable</severity>
1456 <score>-1.0</score>
1457 <shortDescription>This rule requires that the following event types are enabled: 'Metaspace Summary'.</shortDescription>
1458 <longDescription>The Metaspace Live Set Trend rule requires that the following event types are enabled: 'Metaspace Summary'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1459 </rule>
1460 <rule>
1461 <id>JavaBlocking</id>
1462 <severity>Not Applicable</severity>
1463 <score>-1.0</score>
1464 <shortDescription>This rule requires events to be available from the following event types: 'Java Monitor Blocked'.</shortDescription>
1465 <longDescription>The Java Blocking rule requires events to be available from the following event types: 'Java Monitor Blocked'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1466 </rule>
1467 <rule>
1468 <id>LongGcPause</id>
1469 <severity>OK</severity>
1470 <score>0.0</score>
1471 <shortDescription>The application did not cause any long GC pause times.</shortDescription>
1472 <longDescription>The application did not cause any long GC pause times.</longDescription>
1473 </rule>
1474 <rule>
1475 <id>LowOnPhysicalMemory</id>
1476 <severity>Warning</severity>
1477 <score>85.24971081406179</score>
1478 <shortDescription>The maximum amount of used memory was 99.8 % of the physical memory available.</shortDescription>
1479 <longDescription>The maximum amount of used memory was 16 GiB. This is 99.8 % of the 16 GiB of physical memory available. Having little free memory may lead to swapping, which is very expensive. To avoid this, either decrease the memory usage or increase the amount of available memory.</longDescription>
1480 </rule>
1481 <rule>
1482 <id>ManagementAgent</id>
1483 <severity>Warning</severity>
1484 <score>100.0</score>
1485 <shortDescription>Insecure management agent settings: Both password authentication and SSL were disabled.</shortDescription>
1486 <longDescription>The runtime management agent settings were insecure. Both password authentication and SSL were disabled. A remote user who knows (or guesses) the port number and host name will be able to monitor and control the Java application and platform. This is highly discouraged for production systems.<p>See the <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html">Java Monitoring and Management Guide</a> for more information about how to configure the management agent.</longDescription>
1487 </rule>
1488 <rule>
1489 <id>ManyRunningProcesses</id>
1490 <severity>Not Applicable</severity>
1491 <score>-1.0</score>
1492 <shortDescription>This rule requires that the following event types are enabled: 'System Process'.</shortDescription>
1493 <longDescription>The Competing Processes rule requires that the following event types are enabled: 'System Process'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1494 </rule>
1495 <rule>
1496 <id>MetaspaceOom</id>
1497 <severity>Not Applicable</severity>
1498 <score>-1.0</score>
1499 <shortDescription>This rule requires that the following event types are enabled: 'Metaspace Out of Memory'.</shortDescription>
1500 <longDescription>The Metaspace Out of Memory rule requires that the following event types are enabled: 'Metaspace Out of Memory'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1501 </rule>
1502 <rule>
1503 <id>MethodProfiling</id>
1504 <severity>Not Applicable</severity>
1505 <score>-1.0</score>
1506 <shortDescription>This rule requires events to be available from the following event types: 'Method Profiling Sample', 'Recording Setting'.</shortDescription>
1507 <longDescription>The Method Profiling rule requires events to be available from the following event types: 'Method Profiling Sample', 'Recording Setting'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1508 </rule>
1509 <rule>
1510 <id>Options</id>
1511 <severity>OK</severity>
1512 <score>0.0</score>
1513 <shortDescription>No undocumented, deprecated or non-recommended option flags were detected.</shortDescription>
1514 <longDescription>No undocumented, deprecated or non-recommended option flags were detected.</longDescription>
1515 </rule>
1516 <rule>
1517 <id>OverAggressiveRecordingSetting</id>
1518 <severity>OK</severity>
1519 <score>0.0</score>
1520 <shortDescription>No problems were found with the recording settings.</shortDescription>
1521 <longDescription>No problems were found with the recording settings.</longDescription>
1522 </rule>
1523 <rule>
1524 <id>PasswordsInArguments</id>
1525 <severity>OK</severity>
1526 <score>0.0</score>
1527 <shortDescription>The recording does not seem to contain passwords in the application arguments.</shortDescription>
1528 <longDescription>The recording does not seem to contain passwords in the application arguments.</longDescription>
1529 </rule>
1530 <rule>
1531 <id>PasswordsInEnvironment</id>
1532 <severity>Warning</severity>
1533 <score>100.0</score>
1534 <shortDescription>The environment variables in the recording may contain passwords.</shortDescription>
1535 <longDescription>The following suspicious environment variables were found in this recording: <ul><li>P4PASSWD</li></ul><p>They may contain passwords. If you wish to keep having passwords in your environment variables, but want to be able to share recordings without also sharing the passwords, please disable the 'Initial Environment Variable' event.</longDescription>
1536 </rule>
1537 <rule>
1538 <id>PasswordsInSystemProperties</id>
1539 <severity>OK</severity>
1540 <score>0.0</score>
1541 <shortDescription>The recording does not seem to contain passwords in the system properties.</shortDescription>
1542 <longDescription>The recording does not seem to contain passwords in the system properties.</longDescription>
1543 </rule>
1544 <rule>
1545 <id>PrimitiveToObjectConversion</id>
1546 <severity>Not Applicable</severity>
1547 <score>-1.0</score>
1548 <shortDescription>This rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
1549 <longDescription>The Primitive To Object Conversion rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1550 </rule>
1551 <rule>
1552 <id>SocketRead</id>
1553 <severity>Not Applicable</severity>
1554 <score>-1.0</score>
1555 <shortDescription>This rule requires that the following event types are enabled: 'Socket Read'.</shortDescription>
1556 <longDescription>The Socket Read Peak Duration rule requires that the following event types are enabled: 'Socket Read'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1557 </rule>
1558 <rule>
1559 <id>SocketWrite</id>
1560 <severity>Not Applicable</severity>
1561 <score>-1.0</score>
1562 <shortDescription>This rule requires that the following event types are enabled: 'Socket Write'.</shortDescription>
1563 <longDescription>The Socket Write Peak Duration rule requires that the following event types are enabled: 'Socket Write'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1564 </rule>
1565 <rule>
1566 <id>StackdepthSetting</id>
1567 <severity>OK</severity>
1568 <score>0.0</score>
1569 <shortDescription>No stack traces were truncated in this recording.</shortDescription>
1570 <longDescription>No stack traces were truncated in this recording.</longDescription>
1571 </rule>
1572 <rule>
1573 <id>StringDeduplication</id>
1574 <severity>Not Applicable</severity>
1575 <score>-1.0</score>
1576 <shortDescription>This rule requires that the following event types are enabled: 'Heap Summary'.</shortDescription>
1577 <longDescription>The String Deduplication rule requires that the following event types are enabled: 'Heap Summary'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1578 </rule>
1579 <rule>
1580 <id>SystemGc</id>
1581 <severity>Not Applicable</severity>
1582 <score>-1.0</score>
1583 <shortDescription>This rule requires that the following event types are enabled: 'Garbage Collection'.</shortDescription>
1584 <longDescription>The GCs Caused by System.gc() rule requires that the following event types are enabled: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1585 </rule>
1586 <rule>
1587 <id>TlabAllocationRatio</id>
1588 <severity>OK</severity>
1589 <score>0.0</score>
1590 <shortDescription>No object allocations outside of TLABs detected.</shortDescription>
1591 <longDescription>No object allocations outside of TLABs detected.</longDescription>
1592 </rule>
1593 <rule>
1594 <id>VMOperations</id>
1595 <severity>OK</severity>
1596 <score>1.6971702250000003</score>
1597 <shortDescription>No excessively long VM operations were found in this recording (the longest was 67.887 ms).</shortDescription>
1598 <longDescription>No excessively long VM operations were found in this recording (the longest was 67.887 ms).</longDescription>
1599 </rule>
1600 <rule>
1601 <id>biasedLockingRevocation</id>
1602 <severity>Not Applicable</severity>
1603 <score>-1.0</score>
1604 <shortDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.</shortDescription>
1605 <longDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.<p>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>
1606 </rule>
1607 <rule>
1608 <id>biasedLockingRevocationPause</id>
1609 <severity>OK</severity>
1610 <score>0.0</score>
1611 <shortDescription>No revocation of biased locks found.</shortDescription>
1612 <longDescription>No revocation of biased locks found.</longDescription>
1613 </rule>
1614 </report>
1615 <report>
1616 <file>parallel-gc_cpu.jfr</file>
1617 <rule>
1618 <id>Allocations.class</id>
1619 <severity>OK</severity>
1620 <score>0.02670579099297634</score>
1621 <shortDescription>The most allocated class is likely 'java.util.ArrayList'. This is the most common allocation path for that class: <ul><li>JFRImpl.getRecordings() (100 %)</li><li>MetaProducer.onNewChunk()</li><li>JFRImpl.onNewChunk()</li></ul></shortDescription>
1622 <longDescription>The most allocated class is likely 'java.util.ArrayList'. This is the most common allocation path for that class: <ul><li>JFRImpl.getRecordings() (100 %)</li><li>MetaProducer.onNewChunk()</li><li>JFRImpl.onNewChunk()</li></ul><p>Frequently allocated classes are likely good places to start when trying to reduce garbage collections. Look at the aggregated stack traces of the most commonly allocated classes to see if many instances are created along the same call path. Try to reduce the number of instances created by invoking the most commonly taken paths less.</longDescription>
1623 </rule>
1624 <rule>
1625 <id>Allocations.thread</id>
1626 <severity>OK</severity>
1627 <score>0.07261458520440227</score>
1628 <shortDescription>The thread performing the most allocation is likely 'RMI TCP Connection(1)-127.0.0.1'. This is the most common allocation path for that class: <ul><li>ObjectInputStream$BlockDataInputStream.&lt;init&gt;(ObjectInputStream, InputStream) (50 %)</li><li>ObjectInputStream.&lt;init&gt;(InputStream)</li><li>MarshalInputStream.&lt;init&gt;(InputStream)</li><li>ConnectionInputStream.&lt;init&gt;(InputStream)</li><li>StreamRemoteCall.getInputStream()</li><li>Transport.serviceCall(RemoteCall)</li></ul></shortDescription>
1629 <longDescription>The thread performing the most allocation is likely 'RMI TCP Connection(1)-127.0.0.1'. This is the most common allocation path for that class: <ul><li>ObjectInputStream$BlockDataInputStream.&lt;init&gt;(ObjectInputStream, InputStream) (50 %)</li><li>ObjectInputStream.&lt;init&gt;(InputStream)</li><li>MarshalInputStream.&lt;init&gt;(InputStream)</li><li>ConnectionInputStream.&lt;init&gt;(InputStream)</li><li>StreamRemoteCall.getInputStream()</li><li>Transport.serviceCall(RemoteCall)</li></ul><p>Many allocations performed by the same thread might indicate a problem in a multi-threaded program. Look at the aggregated stack traces for the thread with the highest allocation rate. See if the allocation rate can be brought down, or balanced among the active threads.</longDescription>
1630 </rule>
1631 <rule>
1632 <id>ApplicationHalts</id>
1633 <severity>OK</severity>
1634 <score>0.0</score>
1635 <shortDescription>Application efficiency was not highly affected by halts.</shortDescription>
1636 <longDescription>Application efficiency was not highly affected by halts.<p>The highest ratio between application halts and execution time was 0 % during 1 min starting at 4/4/14 11:17:05 AM. 0 % of the halts during the timespan were because of other reasons than GCs.<p>The total halts ratio during the entire recording was 0 %. 0 % of the total halts were because of other reasons than GCs.<p>Enabling the following event types would improve the accuracy of this rule: jdk.SafepointBegin.</longDescription>
1637 </rule>
1638 <rule>
1639 <id>BufferLost</id>
1640 <severity>OK</severity>
1641 <score>0.0</score>
1642 <shortDescription>No Flight Recorder buffers were lost during the recording.</shortDescription>
1643 <longDescription>No Flight Recorder buffers were lost during the recording.</longDescription>
1644 </rule>
1645 <rule>
1646 <id>BytecodeVerification</id>
1647 <severity>OK</severity>
1648 <score>0.0</score>
1649 <shortDescription>The application was running with bytecode verification enabled.</shortDescription>
1650 <longDescription>The application was running with bytecode verification enabled.</longDescription>
1651 </rule>
1652 <rule>
1653 <id>ClassLeak</id>
1654 <severity>Not Applicable</severity>
1655 <score>-1.0</score>
1656 <shortDescription>This rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.</shortDescription>
1657 <longDescription>The Class Leak rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1658 </rule>
1659 <rule>
1660 <id>ClassLoading</id>
1661 <severity>Not Applicable</severity>
1662 <score>-1.0</score>
1663 <shortDescription>This rule requires that the following event types are enabled: 'Class Load'.</shortDescription>
1664 <longDescription>The Class Loading Pressure rule requires that the following event types are enabled: 'Class Load'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1665 </rule>
1666 <rule>
1667 <id>CodeCache</id>
1668 <severity>OK</severity>
1669 <score>2.07672119140625</score>
1670 <shortDescription>No problems with the code cache were detected in the recording.</shortDescription>
1671 <longDescription>No problems with the code cache were detected in the recording.</longDescription>
1672 </rule>
1673 <rule>
1674 <id>CompareCpu</id>
1675 <severity>OK</severity>
1676 <score>9.313225746154785E-7</score>
1677 <shortDescription>An average CPU load of 0 % was caused by other processes during 1.011 s starting at 4/4/14 11:17:07 AM.</shortDescription>
1678 <longDescription>An average CPU load of 0 % was caused by other processes during 1.011 s starting at 4/4/14 11:17:07 AM.</longDescription>
1679 </rule>
1680 <rule>
1681 <id>CompressedOops</id>
1682 <severity>OK</severity>
1683 <score>0.0</score>
1684 <shortDescription>The settings for Compressed Oops were OK.</shortDescription>
1685 <longDescription>The settings for Compressed Oops were OK.</longDescription>
1686 </rule>
1687 <rule>
1688 <id>ContextSwitch</id>
1689 <severity>Not Applicable</severity>
1690 <score>-1.0</score>
1691 <shortDescription>This rule requires events to be available from the following event types: 'Thread Context Switch Rate'.</shortDescription>
1692 <longDescription>The Context Switches rule requires events to be available from the following event types: 'Thread Context Switch Rate'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1693 </rule>
1694 <rule>
1695 <id>DMSIncident</id>
1696 <severity>Not Applicable</severity>
1697 <score>-1.0</score>
1698 <shortDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.</shortDescription>
1699 <longDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.<p>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>
1700 </rule>
1701 <rule>
1702 <id>DebugNonSafepoints</id>
1703 <severity>Information</severity>
1704 <score>50.0</score>
1705 <shortDescription>DebugNonSafepoints was not enabled.</shortDescription>
1706 <longDescription>DebugNonSafepoints was not enabled.<p>If DebugNonSafepoints is not enabled, the method profiling data will be less accurate as threads that are not at safepoints will not be correctly sampled. Use the following JVM flags to enable this: '-XX:+UnlockDiagnosticVMOptions -XX:+DebugNonSafepoints'. There is a slight performance overhead when enabling these flags. For more information see <a href="http://openjdk.java.net/groups/hotspot/docs/RuntimeOverview.html#Thread%20Management|outline">HotSpot Runtime Overview/Thread Management</a>.</longDescription>
1707 </rule>
1708 <rule>
1709 <id>DiscouragedVmOptions</id>
1710 <severity>OK</severity>
1711 <score>0.0</score>
1712 <shortDescription>No problems were found with the VM options.</shortDescription>
1713 <longDescription>No problems were found with the VM options.</longDescription>
1714 </rule>
1715 <rule>
1716 <id>DumpReason</id>
1717 <severity>OK</severity>
1718 <score>0.0</score>
1719 <shortDescription>This recording was not dumped for an exceptional reason.</shortDescription>
1720 <longDescription>This recording was not dumped for an exceptional reason.</longDescription>
1721 </rule>
1722 <rule>
1723 <id>DuplicateFlags</id>
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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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'.<p>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.<p>There are more sampled threads than the amount of hardware threads. This indicates that the application has enough parallelism for the available hardware.<p>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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1770 </rule>
1771 <rule>
1772 <id>FlightRecordingSupport</id>
1773 <severity>Warning</severity>
1774 <score>80.0</score>
1775 <shortDescription>The recording is from an early access build.</shortDescription>
1776 <longDescription>This recording is from an early access build of the JRE (Java HotSpot(TM) Client VM (25.20-b08) for linux-x86 JRE (1.8.0_20-ea-b08), built on Apr 1 2014 19:40:24 by "java_re" with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)). The automated analysis is not supported, and you may see errors when attempting to analyze the recording.</longDescription>
1777 </rule>
1778 <rule>
1779 <id>GcFreedRatio</id>
1780 <severity>OK</severity>
1781 <score>0.0</score>
1782 <shortDescription>Only 0 heap summary events were found, this rule requires at least 10 events to be able to calculate a relevant result. This likely means that only a few garbage collections occurred during the recording. Having few garbage collections is generally a good sign.</shortDescription>
1783 <longDescription>Only 0 heap summary events were found, this rule requires at least 10 events to be able to calculate a relevant result. This likely means that only a few garbage collections occurred during the recording. Having few garbage collections is generally a good sign.</longDescription>
1784 </rule>
1785 <rule>
1786 <id>GcLocker</id>
1787 <severity>OK</severity>
1788 <score>0.0</score>
1789 <shortDescription>The GC Locker did not cause any garbage collections.</shortDescription>
1790 <longDescription>The GC Locker did not cause any garbage collections.</longDescription>
1791 </rule>
1792 <rule>
1793 <id>GcOptions</id>
1794 <severity>Information</severity>
1795 <score>50.0</score>
1796 <shortDescription>The runtime used 2 GC threads on a machine with 1 CPU cores.</shortDescription>
1797 <longDescription>The runtime used 2 GC threads on a machine with 1 CPU cores. It is not optimal to use more GC threads than available cores. Removing the '-XX:ParallelGCThreads' flag will allow the JVM to set the number of GC threads automatically.</longDescription>
1798 </rule>
1799 <rule>
1800 <id>GcPauseRatio</id>
1801 <severity>OK</severity>
1802 <score>0.0</score>
1803 <shortDescription>Application efficiency was not highly affected by GC pauses.</shortDescription>
1804 <longDescription>Application efficiency was not highly affected by GC pauses.<p>The highest ratio between garbage collection pauses and execution time was 0 % during 1 min starting at 4/4/14 11:17:05 AM. The garbage collection pause ratio of the entire recording was 0 %.</longDescription>
1805 </rule>
1806 <rule>
1807 <id>GcStall</id>
1808 <severity>Not Applicable</severity>
1809 <score>-1.0</score>
1810 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
1811 <longDescription>The GC Stall rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1812 </rule>
1813 <rule>
1814 <id>HeapContent</id>
1815 <severity>Not Applicable</severity>
1816 <score>-1.0</score>
1817 <shortDescription>This rule requires that the following event types are enabled: 'Object Count'.</shortDescription>
1818 <longDescription>The Heap Content rule requires that the following event types are enabled: 'Object Count'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1819 </rule>
1820 <rule>
1821 <id>HeapInspectionGc</id>
1822 <severity>Not Applicable</severity>
1823 <score>-1.0</score>
1824 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
1825 <longDescription>The GCs Caused by Heap Inspection rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1826 </rule>
1827 <rule>
1828 <id>HighGc</id>
1829 <severity>OK</severity>
1830 <score>0.0</score>
1831 <shortDescription>The runtime did not spend much time performing garbage collections.</shortDescription>
1832 <longDescription>The runtime did not spend much time performing garbage collections.</longDescription>
1833 </rule>
1834 <rule>
1835 <id>HighJvmCpu</id>
1836 <severity>Information</severity>
1837 <score>27.969203755893627</score>
1838 <shortDescription>This recording contains few profiling samples even though the CPU load is high.</shortDescription>
1839 <longDescription>This recording contains few profiling samples even though the CPU load is high. The profiling data is thus likely not relevant. This might be because the application is running a lot JNI code or that the JVM is spending a lot of time in GC, class loading, JIT compilation etc.</longDescription>
1840 </rule>
1841 <rule>
1842 <id>IncreasingLiveSet</id>
1843 <severity>Not Applicable</severity>
1844 <score>-1.0</score>
1845 <shortDescription>Too few events to calculate the result.</shortDescription>
1846 <longDescription>Too few events to calculate the result.</longDescription>
1847 </rule>
1848 <rule>
1849 <id>IncreasingMetaSpaceLiveSet</id>
1850 <severity>OK</severity>
1851 <score>0.0</score>
1852 <shortDescription>The class data does not seem to increase during the recording.</shortDescription>
1853 <longDescription>The class data does not seem to increase during the recording.</longDescription>
1854 </rule>
1855 <rule>
1856 <id>JavaBlocking</id>
1857 <severity>Not Applicable</severity>
1858 <score>-1.0</score>
1859 <shortDescription>This rule requires events to be available from the following event types: 'Java Monitor Blocked'.</shortDescription>
1860 <longDescription>The Java Blocking rule requires events to be available from the following event types: 'Java Monitor Blocked'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1861 </rule>
1862 <rule>
1863 <id>LongGcPause</id>
1864 <severity>OK</severity>
1865 <score>0.0</score>
1866 <shortDescription>The application did not cause any long GC pause times.</shortDescription>
1867 <longDescription>The application did not cause any long GC pause times.</longDescription>
1868 </rule>
1869 <rule>
1870 <id>LowOnPhysicalMemory</id>
1871 <severity>OK</severity>
1872 <score>0.0</score>
1873 <shortDescription>The system did not run low on physical memory during this recording.</shortDescription>
1874 <longDescription>The system did not run low on physical memory during this recording.</longDescription>
1875 </rule>
1876 <rule>
1877 <id>ManagementAgent</id>
1878 <severity>OK</severity>
1879 <score>0.0</score>
1880 <shortDescription>No problems were found with the management agent settings.</shortDescription>
1881 <longDescription>No problems were found with the management agent settings.</longDescription>
1882 </rule>
1883 <rule>
1884 <id>ManyRunningProcesses</id>
1885 <severity>OK</severity>
1886 <score>23.21768417223916</score>
1887 <shortDescription>137 processes were running while this Flight Recording was made.</shortDescription>
1888 <longDescription>At 4/4/14 11:17:10 AM, a total of 137 other processes were running on the host machine that this Flight Recording was made on.</longDescription>
1889 </rule>
1890 <rule>
1891 <id>MetaspaceOom</id>
1892 <severity>Not Applicable</severity>
1893 <score>-1.0</score>
1894 <shortDescription>This rule requires that the following event types are enabled: 'Metaspace Out of Memory'.</shortDescription>
1895 <longDescription>The Metaspace Out of Memory rule requires that the following event types are enabled: 'Metaspace Out of Memory'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1896 </rule>
1897 <rule>
1898 <id>MethodProfiling</id>
1899 <severity>OK</severity>
1900 <score>0.0</score>
1901 <shortDescription>No methods where optimization would be particularly efficient could be detected.</shortDescription>
1902 <longDescription>No methods where optimization would be particularly efficient could be detected.</longDescription>
1903 </rule>
1904 <rule>
1905 <id>Options</id>
1906 <severity>OK</severity>
1907 <score>0.0</score>
1908 <shortDescription>No undocumented, deprecated or non-recommended option flags were detected.</shortDescription>
1909 <longDescription>No undocumented, deprecated or non-recommended option flags were detected.</longDescription>
1910 </rule>
1911 <rule>
1912 <id>OverAggressiveRecordingSetting</id>
1913 <severity>OK</severity>
1914 <score>0.0</score>
1915 <shortDescription>No problems were found with the recording settings.</shortDescription>
1916 <longDescription>No problems were found with the recording settings.</longDescription>
1917 </rule>
1918 <rule>
1919 <id>PasswordsInArguments</id>
1920 <severity>OK</severity>
1921 <score>0.0</score>
1922 <shortDescription>The recording does not seem to contain passwords in the application arguments.</shortDescription>
1923 <longDescription>The recording does not seem to contain passwords in the application arguments.</longDescription>
1924 </rule>
1925 <rule>
1926 <id>PasswordsInEnvironment</id>
1927 <severity>OK</severity>
1928 <score>0.0</score>
1929 <shortDescription>The recording does not seem to contain passwords in the environment variables.</shortDescription>
1930 <longDescription>The recording does not seem to contain passwords in the environment variables.</longDescription>
1931 </rule>
1932 <rule>
1933 <id>PasswordsInSystemProperties</id>
1934 <severity>OK</severity>
1935 <score>0.0</score>
1936 <shortDescription>The recording does not seem to contain passwords in the system properties.</shortDescription>
1937 <longDescription>The recording does not seem to contain passwords in the system properties.</longDescription>
1938 </rule>
1939 <rule>
1940 <id>PrimitiveToObjectConversion</id>
1941 <severity>Not Applicable</severity>
1942 <score>-1.0</score>
1943 <shortDescription>This rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
1944 <longDescription>The Primitive To Object Conversion rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1945 </rule>
1946 <rule>
1947 <id>SocketRead</id>
1948 <severity>OK</severity>
1949 <score>0.0</score>
1950 <shortDescription>There are no socket read events in this recording.</shortDescription>
1951 <longDescription>There are no socket read events in this recording.<p>Note that there are some socket read patterns with high duration reads that we consider to be normal and are therefore excluded. Such patterns include JMX RMI communication and MQ series.</longDescription>
1952 </rule>
1953 <rule>
1954 <id>SocketWrite</id>
1955 <severity>OK</severity>
1956 <score>0.0</score>
1957 <shortDescription>There are no socket write events in this recording.</shortDescription>
1958 <longDescription>There are no socket write events in this recording.<p>Note that there are some socket write patterns with high duration writes that we consider to be normal and are therefore excluded. Such patterns include JMX RMI communication.</longDescription>
1959 </rule>
1960 <rule>
1961 <id>StackdepthSetting</id>
1962 <severity>OK</severity>
1963 <score>0.0</score>
1964 <shortDescription>No stack traces were truncated in this recording.</shortDescription>
1965 <longDescription>No stack traces were truncated in this recording.</longDescription>
1966 </rule>
1967 <rule>
1968 <id>StringDeduplication</id>
1969 <severity>Not Applicable</severity>
1970 <score>-1.0</score>
1971 <shortDescription>This rule requires events to be available from the following event types: 'Heap Summary'.</shortDescription>
1972 <longDescription>The String Deduplication rule requires events to be available from the following event types: 'Heap Summary'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1973 </rule>
1974 <rule>
1975 <id>SystemGc</id>
1976 <severity>Not Applicable</severity>
1977 <score>-1.0</score>
1978 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
1979 <longDescription>The GCs Caused by System.gc() rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
1980 </rule>
1981 <rule>
1982 <id>TlabAllocationRatio</id>
1983 <severity>OK</severity>
1984 <score>0.0</score>
1985 <shortDescription>No object allocations outside of TLABs detected.</shortDescription>
1986 <longDescription>No object allocations outside of TLABs detected.</longDescription>
1987 </rule>
1988 <rule>
1989 <id>VMOperations</id>
1990 <severity>OK</severity>
1991 <score>0.0</score>
1992 <shortDescription>No excessively long VM operations were found in this recording (the longest was 0 s).</shortDescription>
1993 <longDescription>No excessively long VM operations were found in this recording (the longest was 0 s).</longDescription>
1994 </rule>
1995 <rule>
1996 <id>biasedLockingRevocation</id>
1997 <severity>Not Applicable</severity>
1998 <score>-1.0</score>
1999 <shortDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.</shortDescription>
2000 <longDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.<p>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>
2001 </rule>
2002 <rule>
2003 <id>biasedLockingRevocationPause</id>
2004 <severity>OK</severity>
2005 <score>0.0</score>
2006 <shortDescription>No revocation of biased locks found.</shortDescription>
2007 <longDescription>No revocation of biased locks found.</longDescription>
2008 </rule>
2009 </report>
2010 <report>
2011 <file>parallel-on-singlecpu.jfr</file>
2012 <rule>
2013 <id>Allocations.class</id>
2014 <severity>OK</severity>
2015 <score>0.031334794765092246</score>
2016 <shortDescription>The most allocated class is likely 'java.lang.Object[]'. This is the most common allocation path for that class: <ul><li>AbstractCollection.toArray() (100 %)</li><li>ArrayList.&lt;init&gt;(Collection)</li><li>JFRImpl.getRecordings()</li><li>MetaProducer.onNewChunk()</li><li>JFRImpl.onNewChunk()</li></ul></shortDescription>
2017 <longDescription>The most allocated class is likely 'java.lang.Object[]'. This is the most common allocation path for that class: <ul><li>AbstractCollection.toArray() (100 %)</li><li>ArrayList.&lt;init&gt;(Collection)</li><li>JFRImpl.getRecordings()</li><li>MetaProducer.onNewChunk()</li><li>JFRImpl.onNewChunk()</li></ul><p>Frequently allocated classes are likely good places to start when trying to reduce garbage collections. Look at the aggregated stack traces of the most commonly allocated classes to see if many instances are created along the same call path. Try to reduce the number of instances created by invoking the most commonly taken paths less.</longDescription>
2018 </rule>
2019 <rule>
2020 <id>Allocations.thread</id>
2021 <severity>OK</severity>
2022 <score>0.031334794765092246</score>
2023 <shortDescription>The thread performing the most allocation is likely 'RMI TCP Connection(1)-127.0.0.1'. This is the most common allocation path for that class: <ul><li>Throwable.fillInStackTrace(int) (100 %)</li><li>Throwable.fillInStackTrace()</li><li>Throwable.&lt;init&gt;(String)</li><li>Exception.&lt;init&gt;(String)</li><li>ReflectiveOperationException.&lt;init&gt;(String)</li><li>NoSuchFieldException.&lt;init&gt;(String)</li></ul></shortDescription>
2024 <longDescription>The thread performing the most allocation is likely 'RMI TCP Connection(1)-127.0.0.1'. This is the most common allocation path for that class: <ul><li>Throwable.fillInStackTrace(int) (100 %)</li><li>Throwable.fillInStackTrace()</li><li>Throwable.&lt;init&gt;(String)</li><li>Exception.&lt;init&gt;(String)</li><li>ReflectiveOperationException.&lt;init&gt;(String)</li><li>NoSuchFieldException.&lt;init&gt;(String)</li></ul><p>Many allocations performed by the same thread might indicate a problem in a multi-threaded program. Look at the aggregated stack traces for the thread with the highest allocation rate. See if the allocation rate can be brought down, or balanced among the active threads.</longDescription>
2025 </rule>
2026 <rule>
2027 <id>ApplicationHalts</id>
2028 <severity>OK</severity>
2029 <score>0.0</score>
2030 <shortDescription>Application efficiency was not highly affected by halts.</shortDescription>
2031 <longDescription>Application efficiency was not highly affected by halts.<p>The highest ratio between application halts and execution time was 0 % during 1 min starting at 4/4/14 8:54:33 AM. 0 % of the halts during the timespan were because of other reasons than GCs.<p>The total halts ratio during the entire recording was 0 %. 0 % of the total halts were because of other reasons than GCs.<p>Enabling the following event types would improve the accuracy of this rule: jdk.SafepointBegin.</longDescription>
2032 </rule>
2033 <rule>
2034 <id>BufferLost</id>
2035 <severity>OK</severity>
2036 <score>0.0</score>
2037 <shortDescription>No Flight Recorder buffers were lost during the recording.</shortDescription>
2038 <longDescription>No Flight Recorder buffers were lost during the recording.</longDescription>
2039 </rule>
2040 <rule>
2041 <id>BytecodeVerification</id>
2042 <severity>OK</severity>
2043 <score>0.0</score>
2044 <shortDescription>The application was running with bytecode verification enabled.</shortDescription>
2045 <longDescription>The application was running with bytecode verification enabled.</longDescription>
2046 </rule>
2047 <rule>
2048 <id>ClassLeak</id>
2049 <severity>Not Applicable</severity>
2050 <score>-1.0</score>
2051 <shortDescription>This rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.</shortDescription>
2052 <longDescription>The Class Leak rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2053 </rule>
2054 <rule>
2055 <id>ClassLoading</id>
2056 <severity>Not Applicable</severity>
2057 <score>-1.0</score>
2058 <shortDescription>This rule requires that the following event types are enabled: 'Class Load'.</shortDescription>
2059 <longDescription>The Class Loading Pressure rule requires that the following event types are enabled: 'Class Load'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2060 </rule>
2061 <rule>
2062 <id>CodeCache</id>
2063 <severity>OK</severity>
2064 <score>2.0233154296875</score>
2065 <shortDescription>No problems with the code cache were detected in the recording.</shortDescription>
2066 <longDescription>No problems with the code cache were detected in the recording.</longDescription>
2067 </rule>
2068 <rule>
2069 <id>CompareCpu</id>
2070 <severity>OK</severity>
2071 <score>0.0</score>
2072 <shortDescription>An average CPU load of 0 % was caused by other processes during 1.010 s starting at 4/4/14 8:54:36 AM.</shortDescription>
2073 <longDescription>An average CPU load of 0 % was caused by other processes during 1.010 s starting at 4/4/14 8:54:36 AM.</longDescription>
2074 </rule>
2075 <rule>
2076 <id>CompressedOops</id>
2077 <severity>OK</severity>
2078 <score>0.0</score>
2079 <shortDescription>The settings for Compressed Oops were OK.</shortDescription>
2080 <longDescription>The settings for Compressed Oops were OK.</longDescription>
2081 </rule>
2082 <rule>
2083 <id>ContextSwitch</id>
2084 <severity>OK</severity>
2085 <score>0.0</score>
2086 <shortDescription>The program did not context switch excessively during the recording.</shortDescription>
2087 <longDescription>The program did not context switch excessively during the recording.</longDescription>
2088 </rule>
2089 <rule>
2090 <id>DMSIncident</id>
2091 <severity>Not Applicable</severity>
2092 <score>-1.0</score>
2093 <shortDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.</shortDescription>
2094 <longDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.<p>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>
2095 </rule>
2096 <rule>
2097 <id>DebugNonSafepoints</id>
2098 <severity>Information</severity>
2099 <score>50.0</score>
2100 <shortDescription>DebugNonSafepoints was not enabled.</shortDescription>
2101 <longDescription>DebugNonSafepoints was not enabled.<p>If DebugNonSafepoints is not enabled, the method profiling data will be less accurate as threads that are not at safepoints will not be correctly sampled. Use the following JVM flags to enable this: '-XX:+UnlockDiagnosticVMOptions -XX:+DebugNonSafepoints'. There is a slight performance overhead when enabling these flags. For more information see <a href="http://openjdk.java.net/groups/hotspot/docs/RuntimeOverview.html#Thread%20Management|outline">HotSpot Runtime Overview/Thread Management</a>.</longDescription>
2102 </rule>
2103 <rule>
2104 <id>DiscouragedVmOptions</id>
2105 <severity>OK</severity>
2106 <score>0.0</score>
2107 <shortDescription>No problems were found with the VM options.</shortDescription>
2108 <longDescription>No problems were found with the VM options.</longDescription>
2109 </rule>
2110 <rule>
2111 <id>DumpReason</id>
2112 <severity>OK</severity>
2113 <score>0.0</score>
2114 <shortDescription>This recording was not dumped for an exceptional reason.</shortDescription>
2115 <longDescription>This recording was not dumped for an exceptional reason.</longDescription>
2116 </rule>
2117 <rule>
2118 <id>DuplicateFlags</id>
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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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'.<p>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.<p>There are more sampled threads than the amount of hardware threads. This indicates that the application has enough parallelism for the available hardware.<p>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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2165 </rule>
2166 <rule>
2167 <id>FlightRecordingSupport</id>
2168 <severity>Warning</severity>
2169 <score>80.0</score>
2170 <shortDescription>The recording is from an early access build.</shortDescription>
2171 <longDescription>This recording is from an early access build of the JRE (Java HotSpot(TM) Client VM (25.20-b08) for linux-x86 JRE (1.8.0_20-ea-b08), built on Apr 1 2014 19:40:24 by "java_re" with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)). The automated analysis is not supported, and you may see errors when attempting to analyze the recording.</longDescription>
2172 </rule>
2173 <rule>
2174 <id>GcFreedRatio</id>
2175 <severity>OK</severity>
2176 <score>0.0</score>
2177 <shortDescription>Only 0 heap summary events were found, this rule requires at least 10 events to be able to calculate a relevant result. This likely means that only a few garbage collections occurred during the recording. Having few garbage collections is generally a good sign.</shortDescription>
2178 <longDescription>Only 0 heap summary events were found, this rule requires at least 10 events to be able to calculate a relevant result. This likely means that only a few garbage collections occurred during the recording. Having few garbage collections is generally a good sign.</longDescription>
2179 </rule>
2180 <rule>
2181 <id>GcLocker</id>
2182 <severity>OK</severity>
2183 <score>0.0</score>
2184 <shortDescription>The GC Locker did not cause any garbage collections.</shortDescription>
2185 <longDescription>The GC Locker did not cause any garbage collections.</longDescription>
2186 </rule>
2187 <rule>
2188 <id>GcOptions</id>
2189 <severity>Information</severity>
2190 <score>50.0</score>
2191 <shortDescription>The runtime used a parallel GC on a single-core machine.</shortDescription>
2192 <longDescription>The runtime used a parallel GC on a single-core machine. This is not optimal. Use the <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/vm/gctuning/collectors.html">Serial Collector</a> instead, which is optimized for single-core machines.</longDescription>
2193 </rule>
2194 <rule>
2195 <id>GcPauseRatio</id>
2196 <severity>OK</severity>
2197 <score>0.0</score>
2198 <shortDescription>Application efficiency was not highly affected by GC pauses.</shortDescription>
2199 <longDescription>Application efficiency was not highly affected by GC pauses.<p>The highest ratio between garbage collection pauses and execution time was 0 % during 1 min starting at 4/4/14 8:54:33 AM. The garbage collection pause ratio of the entire recording was 0 %.</longDescription>
2200 </rule>
2201 <rule>
2202 <id>GcStall</id>
2203 <severity>Not Applicable</severity>
2204 <score>-1.0</score>
2205 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
2206 <longDescription>The GC Stall rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2207 </rule>
2208 <rule>
2209 <id>HeapContent</id>
2210 <severity>Not Applicable</severity>
2211 <score>-1.0</score>
2212 <shortDescription>This rule requires that the following event types are enabled: 'Object Count'.</shortDescription>
2213 <longDescription>The Heap Content rule requires that the following event types are enabled: 'Object Count'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2214 </rule>
2215 <rule>
2216 <id>HeapInspectionGc</id>
2217 <severity>Not Applicable</severity>
2218 <score>-1.0</score>
2219 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
2220 <longDescription>The GCs Caused by Heap Inspection rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2221 </rule>
2222 <rule>
2223 <id>HighGc</id>
2224 <severity>OK</severity>
2225 <score>0.0</score>
2226 <shortDescription>The runtime did not spend much time performing garbage collections.</shortDescription>
2227 <longDescription>The runtime did not spend much time performing garbage collections.</longDescription>
2228 </rule>
2229 <rule>
2230 <id>HighJvmCpu</id>
2231 <severity>Information</severity>
2232 <score>35.27744043201552</score>
2233 <shortDescription>This recording contains few profiling samples even though the CPU load is high.</shortDescription>
2234 <longDescription>This recording contains few profiling samples even though the CPU load is high. The profiling data is thus likely not relevant. This might be because the application is running a lot JNI code or that the JVM is spending a lot of time in GC, class loading, JIT compilation etc.</longDescription>
2235 </rule>
2236 <rule>
2237 <id>IncreasingLiveSet</id>
2238 <severity>Not Applicable</severity>
2239 <score>-1.0</score>
2240 <shortDescription>Too few events to calculate the result.</shortDescription>
2241 <longDescription>Too few events to calculate the result.</longDescription>
2242 </rule>
2243 <rule>
2244 <id>IncreasingMetaSpaceLiveSet</id>
2245 <severity>OK</severity>
2246 <score>0.0</score>
2247 <shortDescription>The class data does not seem to increase during the recording.</shortDescription>
2248 <longDescription>The class data does not seem to increase during the recording.</longDescription>
2249 </rule>
2250 <rule>
2251 <id>JavaBlocking</id>
2252 <severity>Not Applicable</severity>
2253 <score>-1.0</score>
2254 <shortDescription>This rule requires events to be available from the following event types: 'Java Monitor Blocked'.</shortDescription>
2255 <longDescription>The Java Blocking rule requires events to be available from the following event types: 'Java Monitor Blocked'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2256 </rule>
2257 <rule>
2258 <id>LongGcPause</id>
2259 <severity>OK</severity>
2260 <score>0.0</score>
2261 <shortDescription>The application did not cause any long GC pause times.</shortDescription>
2262 <longDescription>The application did not cause any long GC pause times.</longDescription>
2263 </rule>
2264 <rule>
2265 <id>LowOnPhysicalMemory</id>
2266 <severity>OK</severity>
2267 <score>0.0</score>
2268 <shortDescription>The system did not run low on physical memory during this recording.</shortDescription>
2269 <longDescription>The system did not run low on physical memory during this recording.</longDescription>
2270 </rule>
2271 <rule>
2272 <id>ManagementAgent</id>
2273 <severity>OK</severity>
2274 <score>0.0</score>
2275 <shortDescription>No problems were found with the management agent settings.</shortDescription>
2276 <longDescription>No problems were found with the management agent settings.</longDescription>
2277 </rule>
2278 <rule>
2279 <id>ManyRunningProcesses</id>
2280 <severity>OK</severity>
2281 <score>23.21768417223916</score>
2282 <shortDescription>137 processes were running while this Flight Recording was made.</shortDescription>
2283 <longDescription>At 4/4/14 8:54:38 AM, a total of 137 other processes were running on the host machine that this Flight Recording was made on.</longDescription>
2284 </rule>
2285 <rule>
2286 <id>MetaspaceOom</id>
2287 <severity>Not Applicable</severity>
2288 <score>-1.0</score>
2289 <shortDescription>This rule requires that the following event types are enabled: 'Metaspace Out of Memory'.</shortDescription>
2290 <longDescription>The Metaspace Out of Memory rule requires that the following event types are enabled: 'Metaspace Out of Memory'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2291 </rule>
2292 <rule>
2293 <id>MethodProfiling</id>
2294 <severity>OK</severity>
2295 <score>0.0</score>
2296 <shortDescription>No methods where optimization would be particularly efficient could be detected.</shortDescription>
2297 <longDescription>No methods where optimization would be particularly efficient could be detected.</longDescription>
2298 </rule>
2299 <rule>
2300 <id>Options</id>
2301 <severity>OK</severity>
2302 <score>0.0</score>
2303 <shortDescription>No undocumented, deprecated or non-recommended option flags were detected.</shortDescription>
2304 <longDescription>No undocumented, deprecated or non-recommended option flags were detected.</longDescription>
2305 </rule>
2306 <rule>
2307 <id>OverAggressiveRecordingSetting</id>
2308 <severity>OK</severity>
2309 <score>0.0</score>
2310 <shortDescription>No problems were found with the recording settings.</shortDescription>
2311 <longDescription>No problems were found with the recording settings.</longDescription>
2312 </rule>
2313 <rule>
2314 <id>PasswordsInArguments</id>
2315 <severity>OK</severity>
2316 <score>0.0</score>
2317 <shortDescription>The recording does not seem to contain passwords in the application arguments.</shortDescription>
2318 <longDescription>The recording does not seem to contain passwords in the application arguments.</longDescription>
2319 </rule>
2320 <rule>
2321 <id>PasswordsInEnvironment</id>
2322 <severity>OK</severity>
2323 <score>0.0</score>
2324 <shortDescription>The recording does not seem to contain passwords in the environment variables.</shortDescription>
2325 <longDescription>The recording does not seem to contain passwords in the environment variables.</longDescription>
2326 </rule>
2327 <rule>
2328 <id>PasswordsInSystemProperties</id>
2329 <severity>OK</severity>
2330 <score>0.0</score>
2331 <shortDescription>The recording does not seem to contain passwords in the system properties.</shortDescription>
2332 <longDescription>The recording does not seem to contain passwords in the system properties.</longDescription>
2333 </rule>
2334 <rule>
2335 <id>PrimitiveToObjectConversion</id>
2336 <severity>Not Applicable</severity>
2337 <score>-1.0</score>
2338 <shortDescription>This rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
2339 <longDescription>The Primitive To Object Conversion rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2340 </rule>
2341 <rule>
2342 <id>SocketRead</id>
2343 <severity>OK</severity>
2344 <score>0.0</score>
2345 <shortDescription>There are no socket read events in this recording.</shortDescription>
2346 <longDescription>There are no socket read events in this recording.<p>Note that there are some socket read patterns with high duration reads that we consider to be normal and are therefore excluded. Such patterns include JMX RMI communication and MQ series.</longDescription>
2347 </rule>
2348 <rule>
2349 <id>SocketWrite</id>
2350 <severity>Not Applicable</severity>
2351 <score>-1.0</score>
2352 <shortDescription>This rule requires events to be available from the following event types: 'Socket Write'.</shortDescription>
2353 <longDescription>The Socket Write Peak Duration rule requires events to be available from the following event types: 'Socket Write'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2354 </rule>
2355 <rule>
2356 <id>StackdepthSetting</id>
2357 <severity>OK</severity>
2358 <score>0.0</score>
2359 <shortDescription>No stack traces were truncated in this recording.</shortDescription>
2360 <longDescription>No stack traces were truncated in this recording.</longDescription>
2361 </rule>
2362 <rule>
2363 <id>StringDeduplication</id>
2364 <severity>Not Applicable</severity>
2365 <score>-1.0</score>
2366 <shortDescription>This rule requires events to be available from the following event types: 'Heap Summary'.</shortDescription>
2367 <longDescription>The String Deduplication rule requires events to be available from the following event types: 'Heap Summary'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2368 </rule>
2369 <rule>
2370 <id>SystemGc</id>
2371 <severity>Not Applicable</severity>
2372 <score>-1.0</score>
2373 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
2374 <longDescription>The GCs Caused by System.gc() rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2375 </rule>
2376 <rule>
2377 <id>TlabAllocationRatio</id>
2378 <severity>OK</severity>
2379 <score>0.0</score>
2380 <shortDescription>No object allocations outside of TLABs detected.</shortDescription>
2381 <longDescription>No object allocations outside of TLABs detected.</longDescription>
2382 </rule>
2383 <rule>
2384 <id>VMOperations</id>
2385 <severity>OK</severity>
2386 <score>0.0</score>
2387 <shortDescription>No excessively long VM operations were found in this recording (the longest was 0 s).</shortDescription>
2388 <longDescription>No excessively long VM operations were found in this recording (the longest was 0 s).</longDescription>
2389 </rule>
2390 <rule>
2391 <id>biasedLockingRevocation</id>
2392 <severity>Not Applicable</severity>
2393 <score>-1.0</score>
2394 <shortDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.</shortDescription>
2395 <longDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.<p>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>
2396 </rule>
2397 <rule>
2398 <id>biasedLockingRevocationPause</id>
2399 <severity>OK</severity>
2400 <score>0.0</score>
2401 <shortDescription>No revocation of biased locks found.</shortDescription>
2402 <longDescription>No revocation of biased locks found.</longDescription>
2403 </rule>
2404 </report>
2405 <report>
2406 <file>stringdedup_enabled_jdk9.jfr</file>
2407 <rule>
2408 <id>Allocations.class</id>
2409 <severity>Not Applicable</severity>
2410 <score>-1.0</score>
2411 <shortDescription>This rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
2412 <longDescription>The Allocated Classes rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2413 </rule>
2414 <rule>
2415 <id>Allocations.thread</id>
2416 <severity>Not Applicable</severity>
2417 <score>-1.0</score>
2418 <shortDescription>This rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
2419 <longDescription>The Threads Allocating rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2420 </rule>
2421 <rule>
2422 <id>ApplicationHalts</id>
2423 <severity>OK</severity>
2424 <score>0.4097173333333334</score>
2425 <shortDescription>Application efficiency was not highly affected by halts.</shortDescription>
2426 <longDescription>Application efficiency was not highly affected by halts.<p>The highest ratio between application halts and execution time was 0.082 % during 1 min starting at 4/24/18 10:08:52 AM. 51.552 % of the halts during the timespan were because of other reasons than GCs.<p>The total halts ratio during the entire recording was 1.003 %. 51.552 % of the total halts were because of other reasons than GCs.</longDescription>
2427 </rule>
2428 <rule>
2429 <id>BufferLost</id>
2430 <severity>OK</severity>
2431 <score>0.0</score>
2432 <shortDescription>No Flight Recorder buffers were lost during the recording.</shortDescription>
2433 <longDescription>No Flight Recorder buffers were lost during the recording.</longDescription>
2434 </rule>
2435 <rule>
2436 <id>BytecodeVerification</id>
2437 <severity>OK</severity>
2438 <score>0.0</score>
2439 <shortDescription>The application was running with bytecode verification enabled.</shortDescription>
2440 <longDescription>The application was running with bytecode verification enabled.</longDescription>
2441 </rule>
2442 <rule>
2443 <id>ClassLeak</id>
2444 <severity>Not Applicable</severity>
2445 <score>-1.0</score>
2446 <shortDescription>This rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.</shortDescription>
2447 <longDescription>The Class Leak rule requires that the following event types are enabled: 'Class Load', 'Class Unload'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2448 </rule>
2449 <rule>
2450 <id>ClassLoading</id>
2451 <severity>Not Applicable</severity>
2452 <score>-1.0</score>
2453 <shortDescription>This rule requires that the following event types are enabled: 'Class Load'.</shortDescription>
2454 <longDescription>The Class Loading Pressure rule requires that the following event types are enabled: 'Class Load'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2455 </rule>
2456 <rule>
2457 <id>CodeCache</id>
2458 <severity>OK</severity>
2459 <score>21.734625758350106</score>
2460 <shortDescription>No problems with the code cache were detected in the recording.</shortDescription>
2461 <longDescription>No problems with the code cache were detected in the recording.</longDescription>
2462 </rule>
2463 <rule>
2464 <id>CompareCpu</id>
2465 <severity>OK</severity>
2466 <score>18.426045491651166</score>
2467 <shortDescription>An average CPU load of 15 % was caused by other processes during 1.060 s starting at 4/24/18 10:08:54 AM.</shortDescription>
2468 <longDescription>An average CPU load of 15 % was caused by other processes during 1.060 s starting at 4/24/18 10:08:54 AM.</longDescription>
2469 </rule>
2470 <rule>
2471 <id>CompressedOops</id>
2472 <severity>OK</severity>
2473 <score>0.0</score>
2474 <shortDescription>The settings for Compressed Oops were OK.</shortDescription>
2475 <longDescription>The settings for Compressed Oops were OK.</longDescription>
2476 </rule>
2477 <rule>
2478 <id>ContextSwitch</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: 'Thread Context Switch Rate'.</shortDescription>
2482 <longDescription>The Context Switches rule requires events to be available from the following event types: 'Thread Context Switch Rate'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2483 </rule>
2484 <rule>
2485 <id>DMSIncident</id>
2486 <severity>Not Applicable</severity>
2487 <score>-1.0</score>
2488 <shortDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.</shortDescription>
2489 <longDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.<p>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>
2490 </rule>
2491 <rule>
2492 <id>DebugNonSafepoints</id>
2493 <severity>OK</severity>
2494 <score>0.0</score>
2495 <shortDescription>DebugNonSafepoints was implicitly enabled in the JVM version used to create this recording.</shortDescription>
2496 <longDescription>DebugNonSafepoints was implicitly enabled in the JVM version used to create this recording.</longDescription>
2497 </rule>
2498 <rule>
2499 <id>DiscouragedVmOptions</id>
2500 <severity>OK</severity>
2501 <score>0.0</score>
2502 <shortDescription>No problems were found with the VM options.</shortDescription>
2503 <longDescription>No problems were found with the VM options.</longDescription>
2504 </rule>
2505 <rule>
2506 <id>DumpReason</id>
2507 <severity>OK</severity>
2508 <score>0.0</score>
2509 <shortDescription>This recording was not dumped for an exceptional reason.</shortDescription>
2510 <longDescription>This recording was not dumped for an exceptional reason.</longDescription>
2511 </rule>
2512 <rule>
2513 <id>DuplicateFlags</id>
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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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'.<p>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).<p>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.<p>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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2560 </rule>
2561 <rule>
2562 <id>FlightRecordingSupport</id>
2563 <severity>OK</severity>
2564 <score>0.0</score>
2565 <shortDescription>The JVM version used for this recording has full Flight Recorder support.</shortDescription>
2566 <longDescription>The JVM version used for this recording has full Flight Recorder support.</longDescription>
2567 </rule>
2568 <rule>
2569 <id>GcFreedRatio</id>
2570 <severity>OK</severity>
2571 <score>0.0</score>
2572 <shortDescription>Only 6 heap summary events were found, this rule requires at least 10 events to be able to calculate a relevant result. This likely means that only a few garbage collections occurred during the recording. Having few garbage collections is generally a good sign.</shortDescription>
2573 <longDescription>Only 6 heap summary events were found, this rule requires at least 10 events to be able to calculate a relevant result. This likely means that only a few garbage collections occurred during the recording. Having few garbage collections is generally a good sign.</longDescription>
2574 </rule>
2575 <rule>
2576 <id>GcLocker</id>
2577 <severity>OK</severity>
2578 <score>0.0</score>
2579 <shortDescription>The GC Locker did not cause any garbage collections.</shortDescription>
2580 <longDescription>The GC Locker did not cause any garbage collections.</longDescription>
2581 </rule>
2582 <rule>
2583 <id>GcOptions</id>
2584 <severity>OK</severity>
2585 <score>0.0</score>
2586 <shortDescription>No problems were found with the GC configuration.</shortDescription>
2587 <longDescription>No problems were found with the GC configuration.</longDescription>
2588 </rule>
2589 <rule>
2590 <id>GcPauseRatio</id>
2591 <severity>OK</severity>
2592 <score>0.1985013333333333</score>
2593 <shortDescription>Application efficiency was not highly affected by GC pauses.</shortDescription>
2594 <longDescription>Application efficiency was not highly affected by GC pauses.<p>The highest ratio between garbage collection pauses and execution time was 0.04 % during 1 min starting at 4/24/18 10:08:52 AM. The garbage collection pause ratio of the entire recording was 0.486 %.</longDescription>
2595 </rule>
2596 <rule>
2597 <id>GcStall</id>
2598 <severity>Not Applicable</severity>
2599 <score>-1.0</score>
2600 <shortDescription>This rule requires events to be available from the following event types: 'Concurrent Mode Failure', 'GC Configuration', 'Garbage Collection'.</shortDescription>
2601 <longDescription>The GC Stall rule requires events to be available from the following event types: 'Concurrent Mode Failure', 'GC Configuration', 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2602 </rule>
2603 <rule>
2604 <id>HeapContent</id>
2605 <severity>Not Applicable</severity>
2606 <score>-1.0</score>
2607 <shortDescription>This rule requires that the following event types are enabled: 'Object Count'.</shortDescription>
2608 <longDescription>The Heap Content rule requires that the following event types are enabled: 'Object Count'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2609 </rule>
2610 <rule>
2611 <id>HeapInspectionGc</id>
2612 <severity>OK</severity>
2613 <score>0.0</score>
2614 <shortDescription>The JVM did not perform any heap inspection GCs.</shortDescription>
2615 <longDescription>The JVM did not perform any heap inspection GCs. This is good since they usually take a lot of time.</longDescription>
2616 </rule>
2617 <rule>
2618 <id>HighGc</id>
2619 <severity>OK</severity>
2620 <score>2.054924803137792</score>
2621 <shortDescription>The JVM was paused for 100 % of the time during 9.017 ms starting at 4/24/18 10:08:53 AM.</shortDescription>
2622 <longDescription>The JVM was paused for 100 % of the time during 9.017 ms starting at 4/24/18 10:08:53 AM. The time spent performing garbage collection may be reduced by increasing the heap size or by trying to reduce allocation.<p>To improve rule accuracy and/or get more details for further investigation, it is recommended to enable the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.</longDescription>
2623 </rule>
2624 <rule>
2625 <id>HighJvmCpu</id>
2626 <severity>OK</severity>
2627 <score>1.4885947328122275</score>
2628 <shortDescription>The JVM does not seem to cause a lot of CPU load.</shortDescription>
2629 <longDescription>The JVM does not seem to cause a lot of CPU load.</longDescription>
2630 </rule>
2631 <rule>
2632 <id>IncreasingLiveSet</id>
2633 <severity>OK</severity>
2634 <score>0.0</score>
2635 <shortDescription>No memory leaks were detected.</shortDescription>
2636 <longDescription>No memory leaks were detected.</longDescription>
2637 </rule>
2638 <rule>
2639 <id>IncreasingMetaSpaceLiveSet</id>
2640 <severity>OK</severity>
2641 <score>0.0</score>
2642 <shortDescription>The class data does not seem to increase during the recording.</shortDescription>
2643 <longDescription>The class data does not seem to increase during the recording.</longDescription>
2644 </rule>
2645 <rule>
2646 <id>JavaBlocking</id>
2647 <severity>Not Applicable</severity>
2648 <score>-1.0</score>
2649 <shortDescription>This rule requires events to be available from the following event types: 'Java Monitor Blocked'.</shortDescription>
2650 <longDescription>The Java Blocking rule requires events to be available from the following event types: 'Java Monitor Blocked'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2651 </rule>
2652 <rule>
2653 <id>LongGcPause</id>
2654 <severity>OK</severity>
2655 <score>0.27457770686965866</score>
2656 <shortDescription>The longest GC pause was 9.017 ms.</shortDescription>
2657 <longDescription>The longest GC pause was 9.017 ms.</longDescription>
2658 </rule>
2659 <rule>
2660 <id>LowOnPhysicalMemory</id>
2661 <severity>Information</severity>
2662 <score>64.30361523113581</score>
2663 <shortDescription>The maximum amount of used memory was 91.8 % of the physical memory available.</shortDescription>
2664 <longDescription>The maximum amount of used memory was 29.3 GiB. This is 91.8 % of the 31.9 GiB of physical memory available. Having little free memory may lead to swapping, which is very expensive. To avoid this, either decrease the memory usage or increase the amount of available memory.</longDescription>
2665 </rule>
2666 <rule>
2667 <id>ManagementAgent</id>
2668 <severity>Not Applicable</severity>
2669 <score>-1.0</score>
2670 <shortDescription>This rule requires that the following event types are enabled: 'Initial System Property'.</shortDescription>
2671 <longDescription>The Discouraged Management Agent Settings rule requires that the following event types are enabled: 'Initial System Property'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2672 </rule>
2673 <rule>
2674 <id>ManyRunningProcesses</id>
2675 <severity>Not Applicable</severity>
2676 <score>-1.0</score>
2677 <shortDescription>This rule requires that the following event types are enabled: 'System Process'.</shortDescription>
2678 <longDescription>The Competing Processes rule requires that the following event types are enabled: 'System Process'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2679 </rule>
2680 <rule>
2681 <id>MetaspaceOom</id>
2682 <severity>OK</severity>
2683 <score>0.0</score>
2684 <shortDescription>The metaspace was not exhausted during this recording.</shortDescription>
2685 <longDescription>The metaspace was not exhausted during this recording.</longDescription>
2686 </rule>
2687 <rule>
2688 <id>MethodProfiling</id>
2689 <severity>OK</severity>
2690 <score>0.0</score>
2691 <shortDescription>No methods where optimization would be particularly efficient could be detected.</shortDescription>
2692 <longDescription>No methods where optimization would be particularly efficient could be detected.</longDescription>
2693 </rule>
2694 <rule>
2695 <id>Options</id>
2696 <severity>OK</severity>
2697 <score>0.0</score>
2698 <shortDescription>No undocumented, deprecated or non-recommended option flags were detected.</shortDescription>
2699 <longDescription>No undocumented, deprecated or non-recommended option flags were detected.</longDescription>
2700 </rule>
2701 <rule>
2702 <id>OverAggressiveRecordingSetting</id>
2703 <severity>Not Applicable</severity>
2704 <score>-1.0</score>
2705 <shortDescription>This rule requires that the following event types are enabled: 'Initial System Property'.</shortDescription>
2706 <longDescription>The Discouraged Recording Settings rule requires that the following event types are enabled: 'Initial System Property'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2707 </rule>
2708 <rule>
2709 <id>PasswordsInArguments</id>
2710 <severity>OK</severity>
2711 <score>0.0</score>
2712 <shortDescription>The recording does not seem to contain passwords in the application arguments.</shortDescription>
2713 <longDescription>The recording does not seem to contain passwords in the application arguments.</longDescription>
2714 </rule>
2715 <rule>
2716 <id>PasswordsInEnvironment</id>
2717 <severity>Not Applicable</severity>
2718 <score>-1.0</score>
2719 <shortDescription>This rule requires that the following event types are enabled: 'Initial Environment Variable'.</shortDescription>
2720 <longDescription>The Passwords in Environment Variables rule requires that the following event types are enabled: 'Initial Environment Variable'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2721 </rule>
2722 <rule>
2723 <id>PasswordsInSystemProperties</id>
2724 <severity>Not Applicable</severity>
2725 <score>-1.0</score>
2726 <shortDescription>This rule requires that the following event types are enabled: 'Initial System Property'.</shortDescription>
2727 <longDescription>The Passwords in System Properties rule requires that the following event types are enabled: 'Initial System Property'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2728 </rule>
2729 <rule>
2730 <id>PrimitiveToObjectConversion</id>
2731 <severity>Not Applicable</severity>
2732 <score>-1.0</score>
2733 <shortDescription>This rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
2734 <longDescription>The Primitive To Object Conversion rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2735 </rule>
2736 <rule>
2737 <id>SocketRead</id>
2738 <severity>Not Applicable</severity>
2739 <score>-1.0</score>
2740 <shortDescription>This rule requires events to be available from the following event types: 'Socket Read'.</shortDescription>
2741 <longDescription>The Socket Read Peak Duration rule requires events to be available from the following event types: 'Socket Read'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2742 </rule>
2743 <rule>
2744 <id>SocketWrite</id>
2745 <severity>Not Applicable</severity>
2746 <score>-1.0</score>
2747 <shortDescription>This rule requires events to be available from the following event types: 'Socket Write'.</shortDescription>
2748 <longDescription>The Socket Write Peak Duration rule requires events to be available from the following event types: 'Socket Write'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2749 </rule>
2750 <rule>
2751 <id>StackdepthSetting</id>
2752 <severity>OK</severity>
2753 <score>0.0</score>
2754 <shortDescription>No stack traces were truncated in this recording.</shortDescription>
2755 <longDescription>No stack traces were truncated in this recording.</longDescription>
2756 </rule>
2757 <rule>
2758 <id>StringDeduplication</id>
2759 <severity>OK</severity>
2760 <score>0.0</score>
2761 <shortDescription>String deduplication is already enabled.</shortDescription>
2762 <longDescription>String deduplication is already enabled.</longDescription>
2763 </rule>
2764 <rule>
2765 <id>SystemGc</id>
2766 <severity>OK</severity>
2767 <score>0.0</score>
2768 <shortDescription>No garbage collections were caused by System.gc().</shortDescription>
2769 <longDescription>No garbage collections were caused by System.gc().</longDescription>
2770 </rule>
2771 <rule>
2772 <id>TlabAllocationRatio</id>
2773 <severity>Not Applicable</severity>
2774 <score>-1.0</score>
2775 <shortDescription>This rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
2776 <longDescription>The TLAB Allocation Ratio rule requires that the following event types are enabled: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2777 </rule>
2778 <rule>
2779 <id>VMOperations</id>
2780 <severity>OK</severity>
2781 <score>0.6336485833333333</score>
2782 <shortDescription>No excessively long VM operations were found in this recording (the longest was 25.346 ms).</shortDescription>
2783 <longDescription>No excessively long VM operations were found in this recording (the longest was 25.346 ms).</longDescription>
2784 </rule>
2785 <rule>
2786 <id>biasedLockingRevocation</id>
2787 <severity>Not Applicable</severity>
2788 <score>-1.0</score>
2789 <shortDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.</shortDescription>
2790 <longDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.<p>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>
2791 </rule>
2792 <rule>
2793 <id>biasedLockingRevocationPause</id>
2794 <severity>OK</severity>
2795 <score>0.0</score>
2796 <shortDescription>No revocation of biased locks found.</shortDescription>
2797 <longDescription>No revocation of biased locks found.</longDescription>
2798 </rule>
2799 </report>
2800 <report>
2801 <file>wldf.jfr</file>
2802 <rule>
2803 <id>Allocations.class</id>
2804 <severity>Information</severity>
2805 <score>46.750432285649964</score>
2806 <shortDescription>The most allocated class is likely 'char[]'. This is the most common allocation path for that class: <ul><li>Arrays.copyOfRange(char[], int, int) (44.9 %)</li></ul></shortDescription>
2807 <longDescription>The most allocated class is likely 'char[]'. This is the most common allocation path for that class: <ul><li>Arrays.copyOfRange(char[], int, int) (44.9 %)</li></ul><p>Frequently allocated classes are likely good places to start when trying to reduce garbage collections. Look at the aggregated stack traces of the most commonly allocated classes to see if many instances are created along the same call path. Try to reduce the number of instances created by invoking the most commonly taken paths less.</longDescription>
2808 </rule>
2809 <rule>
2810 <id>Allocations.thread</id>
2811 <severity>OK</severity>
2812 <score>24.595150095883856</score>
2813 <shortDescription>The thread performing the most allocation is likely '[ACTIVE] ExecuteThread: &#39;5&#39; for queue: &#39;weblogic.kernel.Default (self-tuning)&#39;'. This is the most common allocation path for that class: <ul><li>Arrays.copyOfRange(char[], int, int) (53.3 %)</li></ul></shortDescription>
2814 <longDescription>The thread performing the most allocation is likely '[ACTIVE] ExecuteThread: &#39;5&#39; for queue: &#39;weblogic.kernel.Default (self-tuning)&#39;'. This is the most common allocation path for that class: <ul><li>Arrays.copyOfRange(char[], int, int) (53.3 %)</li></ul><p>Many allocations performed by the same thread might indicate a problem in a multi-threaded program. Look at the aggregated stack traces for the thread with the highest allocation rate. See if the allocation rate can be brought down, or balanced among the active threads.</longDescription>
2815 </rule>
2816 <rule>
2817 <id>ApplicationHalts</id>
2818 <severity>OK</severity>
2819 <score>11.086075208333334</score>
2820 <shortDescription>Application efficiency was not highly affected by halts.</shortDescription>
2821 <longDescription>Application efficiency was not highly affected by halts.<p>The highest ratio between application halts and execution time was 2.217 % during 1 min starting at 9/24/15 10:08:56 AM. 0.027 % of the halts during the timespan were because of other reasons than GCs.<p>The total halts ratio during the entire recording was 1.882 %. 0.021 % of the total halts were because of other reasons than GCs.<p>Enabling the following event types would improve the accuracy of this rule: jdk.SafepointBegin.</longDescription>
2822 </rule>
2823 <rule>
2824 <id>BufferLost</id>
2825 <severity>OK</severity>
2826 <score>0.0</score>
2827 <shortDescription>No Flight Recorder buffers were lost during the recording.</shortDescription>
2828 <longDescription>No Flight Recorder buffers were lost during the recording.</longDescription>
2829 </rule>
2830 <rule>
2831 <id>BytecodeVerification</id>
2832 <severity>OK</severity>
2833 <score>1.0</score>
2834 <shortDescription>The application was running WebLogic Server with bytecode verification disabled.</shortDescription>
2835 <longDescription>The application was running WebLogic Server with bytecode verification disabled. While not generally recommended, it is considered OK for WLS.</longDescription>
2836 </rule>
2837 <rule>
2838 <id>ClassLeak</id>
2839 <severity>Information</severity>
2840 <score>74.99995410111316</score>
2841 <shortDescription>The difference between the number of times a class has been loaded and the number it has been unloaded, has exceeded the user specified limit. Most loaded: java.lang.Object (258)</shortDescription>
2842 <longDescription>Some classes have been loaded multiple times, and the difference between the number of times a class have been loaded and the number of times it has been unloaded has exceeded the user specified limit. This in itself need not be a problem, but check to see if you expect these classes to be loaded multiple times to make sure that you do not have a class loader leak.<p>Top 5 loaded classes:</p><p><ul><li>java.lang.Object (258)</li><li>java.lang.String (95)</li><li>java.lang.Class (81)</li><li>java.lang.Integer (52)</li><li>oracle.jrockit.jfr.VMJFR (46)</li></ul></p></longDescription>
2843 </rule>
2844 <rule>
2845 <id>ClassLoading</id>
2846 <severity>OK</severity>
2847 <score>0.0</score>
2848 <shortDescription>No significant time was spent loading new classes during this recording.</shortDescription>
2849 <longDescription>No significant time was spent loading new classes during this recording.</longDescription>
2850 </rule>
2851 <rule>
2852 <id>CodeCache</id>
2853 <severity>OK</severity>
2854 <score>16.62089029947917</score>
2855 <shortDescription>No problems with the code cache were detected in the recording.</shortDescription>
2856 <longDescription>No problems with the code cache were detected in the recording.</longDescription>
2857 </rule>
2858 <rule>
2859 <id>CompareCpu</id>
2860 <severity>Warning</severity>
2861 <score>88.51583907913424</score>
2862 <shortDescription>An average CPU load of 54 % was caused by other processes during 4.938 s starting at 9/24/15 10:08:17 AM.</shortDescription>
2863 <longDescription>An average CPU load of 54 % was caused by other processes during 4.938 s starting at 9/24/15 10:08:17 AM.<p>The application performance can be affected if there are other processes that use CPU or other resources on the same computer. To profile representatively or get higher throughput, shut down other resource intensive processes running on the machine.</longDescription>
2864 </rule>
2865 <rule>
2866 <id>CompressedOops</id>
2867 <severity>OK</severity>
2868 <score>0.0</score>
2869 <shortDescription>The settings for Compressed Oops were OK.</shortDescription>
2870 <longDescription>The settings for Compressed Oops were OK.</longDescription>
2871 </rule>
2872 <rule>
2873 <id>ContextSwitch</id>
2874 <severity>OK</severity>
2875 <score>0.0</score>
2876 <shortDescription>The program did not context switch excessively during the recording.</shortDescription>
2877 <longDescription>The program did not context switch excessively during the recording.</longDescription>
2878 </rule>
2879 <rule>
2880 <id>DMSIncident</id>
2881 <severity>Not Applicable</severity>
2882 <score>-1.0</score>
2883 <shortDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.</shortDescription>
2884 <longDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.<p>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>
2885 </rule>
2886 <rule>
2887 <id>DebugNonSafepoints</id>
2888 <severity>Information</severity>
2889 <score>50.0</score>
2890 <shortDescription>DebugNonSafepoints was not enabled.</shortDescription>
2891 <longDescription>DebugNonSafepoints was not enabled.<p>If DebugNonSafepoints is not enabled, the method profiling data will be less accurate as threads that are not at safepoints will not be correctly sampled. Use the following JVM flags to enable this: '-XX:+UnlockDiagnosticVMOptions -XX:+DebugNonSafepoints'. There is a slight performance overhead when enabling these flags. For more information see <a href="http://openjdk.java.net/groups/hotspot/docs/RuntimeOverview.html#Thread%20Management|outline">HotSpot Runtime Overview/Thread Management</a>.</longDescription>
2892 </rule>
2893 <rule>
2894 <id>DiscouragedVmOptions</id>
2895 <severity>OK</severity>
2896 <score>0.0</score>
2897 <shortDescription>No problems were found with the VM options.</shortDescription>
2898 <longDescription>No problems were found with the VM options.</longDescription>
2899 </rule>
2900 <rule>
2901 <id>DumpReason</id>
2902 <severity>OK</severity>
2903 <score>0.0</score>
2904 <shortDescription>This recording was not dumped for an exceptional reason.</shortDescription>
2905 <longDescription>This recording was not dumped for an exceptional reason.</longDescription>
2906 </rule>
2907 <rule>
2908 <id>DuplicateFlags</id>
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: <ul><li>-Djava.endorsed.dirs=c:\java\JDK18~1.0_6\jre\lib\endorsed;C:\tmp\WLS-JFR\oracle_common\modules\endorsed, -Djava.endorsed.dirs=c:\java\JDK18~1.0_6\jre\lib\endorsed;C:\tmp\WLS-JFR\oracle_common\modules\endorsed</li><li>-Xverify:none, -Xverify:none</li></ul></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.<p>The most common error was 'java.lang.NoSuchMethodError', which was thrown 13 times.<p>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'.<p>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.<p>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>
2956 <rule>
2957 <id>FlightRecordingSupport</id>
2958 <severity>OK</severity>
2959 <score>0.0</score>
2960 <shortDescription>The JVM version used for this recording has full Flight Recorder support.</shortDescription>
2961 <longDescription>The JVM version used for this recording has full Flight Recorder support.</longDescription>
2962 </rule>
2963 <rule>
2964 <id>GcFreedRatio</id>
2965 <severity>OK</severity>
2966 <score>1.4318707405222828</score>
2967 <shortDescription>The ratio between memory freed by garbage collections per second and liveset is 0.5. This is likely a reasonable amount.</shortDescription>
2968 <longDescription>61.4 MiB per second was freed by garbage collections during 10 s starting at 9/24/15 10:09:18 AM. This is 0.474 times the average liveset which was 130 MiB. This is likely a reasonable amount.</longDescription>
2969 </rule>
2970 <rule>
2971 <id>GcLocker</id>
2972 <severity>OK</severity>
2973 <score>0.0</score>
2974 <shortDescription>The GC Locker did not cause any garbage collections.</shortDescription>
2975 <longDescription>The GC Locker did not cause any garbage collections.</longDescription>
2976 </rule>
2977 <rule>
2978 <id>GcOptions</id>
2979 <severity>OK</severity>
2980 <score>0.0</score>
2981 <shortDescription>No problems were found with the GC configuration.</shortDescription>
2982 <longDescription>No problems were found with the GC configuration.</longDescription>
2983 </rule>
2984 <rule>
2985 <id>GcPauseRatio</id>
2986 <severity>OK</severity>
2987 <score>11.083072308333335</score>
2988 <shortDescription>Application efficiency was not highly affected by GC pauses.</shortDescription>
2989 <longDescription>Application efficiency was not highly affected by GC pauses.<p>The highest ratio between garbage collection pauses and execution time was 2.217 % during 1 min starting at 9/24/15 10:08:56 AM. The garbage collection pause ratio of the entire recording was 1.882 %.</longDescription>
2990 </rule>
2991 <rule>
2992 <id>GcStall</id>
2993 <severity>Not Applicable</severity>
2994 <score>-1.0</score>
2995 <shortDescription>This rule requires events to be available from the following event types: 'Concurrent Mode Failure', 'GC Configuration', 'Garbage Collection'.</shortDescription>
2996 <longDescription>The GC Stall rule requires events to be available from the following event types: 'Concurrent Mode Failure', 'GC Configuration', 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
2997 </rule>
2998 <rule>
2999 <id>HeapContent</id>
3000 <severity>Warning</severity>
3001 <score>91.23973830878204</score>
3002 <shortDescription>Most of the heap was used by only a few classes.</shortDescription>
3003 <longDescription>Most of the heap was used by only a few classes. If the heap usage needs to be reduced, then this would be a good place to start.</longDescription>
3004 </rule>
3005 <rule>
3006 <id>HeapInspectionGc</id>
3007 <severity>Information</severity>
3008 <score>59.77379177936154</score>
3009 <shortDescription>The JVM performed 4 heap inspection garbage collections.</shortDescription>
3010 <longDescription>The JVM performed 4 heap inspection garbage collections. Performing heap inspection garbage collections may be a problem since they usually take a lot of time.<p>Some of these inspections were caused by the 'Object Count' JFR event. It triggers a full garbage collection at the beginning and end of every recording where that event is enabled. If recordings are only made on demand or not too often, then these garbage collections are usually not a problem since the resulting pauses are not part of the normal application behavior. If recordings are collected often, for example by automatic scripts, or if the application is sensitive to pauses, then it might become an issue. In that case you can consider disabling the 'Object Count' event.</longDescription>
3011 </rule>
3012 <rule>
3013 <id>HighGc</id>
3014 <severity>Information</severity>
3015 <score>72.91379413109293</score>
3016 <shortDescription>The JVM was paused for 100 % of the time during 567.258 ms starting at 9/24/15 10:07:58 AM.</shortDescription>
3017 <longDescription>The JVM was paused for 100 % of the time during 567.258 ms starting at 9/24/15 10:07:58 AM. The time spent performing garbage collection may be reduced by increasing the heap size or by trying to reduce allocation.</longDescription>
3018 </rule>
3019 <rule>
3020 <id>HighJvmCpu</id>
3021 <severity>OK</severity>
3022 <score>13.536580012735357</score>
3023 <shortDescription>The JVM does not seem to cause a lot of CPU load.</shortDescription>
3024 <longDescription>The JVM does not seem to cause a lot of CPU load.</longDescription>
3025 </rule>
3026 <rule>
3027 <id>IncreasingLiveSet</id>
3028 <severity>Information</severity>
3029 <score>58.89187525739308</score>
3030 <shortDescription>The live set on the heap seems to increase with a speed of about 638 KiB per second during the recording.</shortDescription>
3031 <longDescription>The live set on the heap seems to increase with a speed of about 638 KiB per second during the recording.<p>This may be due to a memory leak in the application or it may be an artifact of a short recording. More information can be gathered by using the 'Old Object Sample' event, if available.</longDescription>
3032 </rule>
3033 <rule>
3034 <id>IncreasingMetaSpaceLiveSet</id>
3035 <severity>Information</severity>
3036 <score>56.00212873123657</score>
3037 <shortDescription>The class data seems to increase constantly in the metaspace during the recording.</shortDescription>
3038 <longDescription>The class data seems to increase constantly in the metaspace during the recording. This behavior may indicate a memory leak in the metaspace, this could be due to the application not unloading classes as needed.</longDescription>
3039 </rule>
3040 <rule>
3041 <id>JavaBlocking</id>
3042 <severity>Information</severity>
3043 <score>62.05152332723372</score>
3044 <shortDescription>Threads in the application were blocked on locks for a total time of 1 min 26 s.</shortDescription>
3045 <longDescription>Threads in the application were blocked on locks for a total time of 1 min 26 s. The most common monitor class was 'Logger', which was blocked on 1,612 times.<p>The following regular expression was used to exclude threads from this rule: '(.*weblogic\.socket\.Muxer.*)'</longDescription>
3046 </rule>
3047 <rule>
3048 <id>LongGcPause</id>
3049 <severity>OK</severity>
3050 <score>15.646056210732606</score>
3051 <shortDescription>The longest GC pause was 576.207 ms.</shortDescription>
3052 <longDescription>The longest GC pause was 576.207 ms.</longDescription>
3053 </rule>
3054 <rule>
3055 <id>LowOnPhysicalMemory</id>
3056 <severity>OK</severity>
3057 <score>0.0</score>
3058 <shortDescription>The system did not run low on physical memory during this recording.</shortDescription>
3059 <longDescription>The system did not run low on physical memory during this recording.</longDescription>
3060 </rule>
3061 <rule>
3062 <id>ManagementAgent</id>
3063 <severity>OK</severity>
3064 <score>0.0</score>
3065 <shortDescription>No problems were found with the management agent settings.</shortDescription>
3066 <longDescription>No problems were found with the management agent settings.</longDescription>
3067 </rule>
3068 <rule>
3069 <id>ManyRunningProcesses</id>
3070 <severity>Not Applicable</severity>
3071 <score>-1.0</score>
3072 <shortDescription>This rule requires that the following event types are enabled: 'System Process'.</shortDescription>
3073 <longDescription>The Competing Processes rule requires that the following event types are enabled: 'System Process'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3074 </rule>
3075 <rule>
3076 <id>MetaspaceOom</id>
3077 <severity>OK</severity>
3078 <score>0.0</score>
3079 <shortDescription>The metaspace was not exhausted during this recording.</shortDescription>
3080 <longDescription>The metaspace was not exhausted during this recording.</longDescription>
3081 </rule>
3082 <rule>
3083 <id>MethodProfiling</id>
3084 <severity>OK</severity>
3085 <score>1.0227792539479768</score>
3086 <shortDescription>No methods where optimization would be particularly efficient could be detected.</shortDescription>
3087 <longDescription>No methods where optimization would be particularly efficient could be detected.</longDescription>
3088 </rule>
3089 <rule>
3090 <id>Options</id>
3091 <severity>Information</severity>
3092 <score>74.0</score>
3093 <shortDescription>Deprecated option flags were detected.</shortDescription>
3094 <longDescription>The following option flags are or will be deprecated. Deprecated option flags should be avoided. In some cases they enable legacy code and in other cases they are ignored completely. They will usually be removed in a later Java release.<ul><li>-XX:PermSize=128m: Ignored in Java 8 and removed in Java 9. PermGen was removed in JDK 8, since Java users should not need to know up front how much memory to reserve for class metadata etc. Just like in the JRockit and J9 JVMs, native memory is now used for class metadata, and it will dynamically grow as needed. The equivalent of java.lang.OutOfMemoryError: PermGen will be much harder to provoke. To influence when to start attempting to reclaim metaspace memory, check out the <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">MaxMetaspaceSize flag</a>.</li><li>-XX:MaxPermSize=256m: Ignored in Java 8 and removed in Java 9. PermGen was removed in JDK 8, since Java users should not need to know up front how much memory to reserve for class metadata etc. Just like in the JRockit and J9 JVMs, native memory is now used for class metadata, and it will dynamically grow as needed. The equivalent of java.lang.OutOfMemoryError: PermGen will be much harder to provoke. To influence when to start attempting to reclaim metaspace memory, check out the <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">MaxMetaspaceSize flag</a>.</li></ul></longDescription>
3095 </rule>
3096 <rule>
3097 <id>OverAggressiveRecordingSetting</id>
3098 <severity>OK</severity>
3099 <score>0.0</score>
3100 <shortDescription>No problems were found with the recording settings.</shortDescription>
3101 <longDescription>No problems were found with the recording settings.</longDescription>
3102 </rule>
3103 <rule>
3104 <id>PasswordsInArguments</id>
3105 <severity>OK</severity>
3106 <score>0.0</score>
3107 <shortDescription>The recording does not seem to contain passwords in the application arguments.</shortDescription>
3108 <longDescription>The recording does not seem to contain passwords in the application arguments.</longDescription>
3109 </rule>
3110 <rule>
3111 <id>PasswordsInEnvironment</id>
3112 <severity>Not Applicable</severity>
3113 <score>-1.0</score>
3114 <shortDescription>This rule requires that the following event types are enabled: 'Initial Environment Variable'.</shortDescription>
3115 <longDescription>The Passwords in Environment Variables rule requires that the following event types are enabled: 'Initial Environment Variable'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3116 </rule>
3117 <rule>
3118 <id>PasswordsInSystemProperties</id>
3119 <severity>OK</severity>
3120 <score>0.0</score>
3121 <shortDescription>The recording does not seem to contain passwords in the system properties.</shortDescription>
3122 <longDescription>The recording does not seem to contain passwords in the system properties.</longDescription>
3123 </rule>
3124 <rule>
3125 <id>PrimitiveToObjectConversion</id>
3126 <severity>OK</severity>
3127 <score>0.11127751568911523</score>
3128 <shortDescription>0 % of the total allocation (1.88 MiB) is caused by conversion from primitive types to object types. The most common object type that primitives are converted into is 'java.lang.Integer'.</shortDescription>
3129 <longDescription>0 % of the total allocation (1.88 MiB) is caused by conversion from primitive types to object types.<p>The most common object type that primitives are converted into is 'java.lang.Integer', which causes 1.11 MiB to be allocated. The most common call site is 'weblogic.socket.NIOSocketMuxer$NIOOutputStream.initPool():887'.<p>Conversion from primitives to the corresponding object types can either be done explicitly, or be caused by autoboxing. If a considerable amount of the total allocation is caused by such conversions, consider changing the application source code to avoid this behavior. Look at the allocation stack traces to see which parts of the code to change. This rule finds the calls to the valueOf method for any of the eight object types that have primitive counterparts.</longDescription>
3130 </rule>
3131 <rule>
3132 <id>SocketRead</id>
3133 <severity>OK</severity>
3134 <score>9.634721636363636</score>
3135 <shortDescription>No long socket read pauses were found in this recording (the longest was 105.982 ms).</shortDescription>
3136 <longDescription>No long socket read pauses were found in this recording (the longest was 105.982 ms).<p>Note that there are some socket read patterns with high duration reads that we consider to be normal and are therefore excluded. Such patterns include JMX RMI communication and MQ series.</longDescription>
3137 </rule>
3138 <rule>
3139 <id>SocketWrite</id>
3140 <severity>Information</severity>
3141 <score>28.486599569171002</score>
3142 <shortDescription>There are long socket write pauses in this recording (the longest is 349.745 ms).</shortDescription>
3143 <longDescription>The longest recorded socket write took 349.745 ms to write 81 B to the host at 10.161.190.213. Note that there are some socket write patterns with high duration writes that we consider to be normal and are therefore excluded. Such patterns include JMX RMI communication.</longDescription>
3144 </rule>
3145 <rule>
3146 <id>StackdepthSetting</id>
3147 <severity>Warning</severity>
3148 <score>99.99654514135385</score>
3149 <shortDescription>Some stack traces were truncated in this recording.</shortDescription>
3150 <longDescription>Some stack traces were truncated in this recording.<p>The Flight Recorder only records traces with a depth up to the maximum stack depth value set to 64. This is the default depth. 35.7 % of all traces were larger than this option, and were therefore truncated. If more detailed traces are required, increase the '-XX:FlightRecorderOptions=stackdepth=&lt;value&gt;' value.<p>Events of the following types have truncated stack traces:<ul><li>Allocation in new TLAB (42.4 % truncated traces)</li><li>Class Load (42.8 % truncated traces)</li><li>Allocation outside TLAB (60.7 % truncated traces)</li><li>EJB Pool Manager Pre Invoke (47.1 % truncated traces)</li><li>EJB Business Method Invoke (47.1 % truncated traces)</li><li>EJB Business Method Post Invoke Cleanup (47.1 % truncated traces)</li><li>EJB Pool Manager Post Invoke (47.1 % truncated traces)</li><li>EJB Business Method Post Invoke (44.4 % truncated traces)</li><li>EJB Business Method Pre Invoke (44.4 % truncated traces)</li><li>Servlet Execute (26.2 % truncated traces)</li><li>Servlet Request Dispatch (45 % truncated traces)</li><li>Method Profiling Sample (24.3 % truncated traces)</li><li>JTA Transaction Start (80 % truncated traces)</li><li>JDBC Transaction Start (100 % truncated traces)</li><li>JDBC Statement Creation (54.4 % truncated traces)</li><li>JDBC Connection Prepare (54.4 % truncated traces)</li><li>JDBC Statement Execute (54.4 % truncated traces)</li><li>JDBC Statement Execute Begin (54.4 % truncated traces)</li><li>JDBC Connection Close (73 % truncated traces)</li><li>JTA Transaction End (51.5 % truncated traces)</li><li>JTA Transaction Commit (51 % truncated traces)</li><li>JDBC Connection Release (65 % truncated traces)</li><li>JDBC Transaction Commit (65 % truncated traces)</li><li>JDBC Transaction End (65.6 % truncated traces)</li><li>Socket Read (41.6 % truncated traces)</li><li>File Write (32.6 % truncated traces)</li><li>Java Error (29.1 % truncated traces)</li><li>Webservices JAXRPC Client Request (45.4 % truncated traces)</li><li>Webservices JAXRPC Client Response (100 % truncated traces)</li><li>Java Monitor Blocked (1.09 % truncated traces)</li><li>EJB PoolManager Create (32.7 % truncated traces)</li><li>Allocation Requiring GC (31.6 % truncated traces)</li><li>JDBC Transaction Is Same RM (6.59 % truncated traces)</li><li>Servlet Response Write Headers (0.753 % truncated traces)</li><li>Socket Write (20.6 % truncated traces)</li><li>Java Monitor Wait (0.134 % truncated traces)</li><li>File Read (100 % truncated traces)</li><li>Java Thread Sleep (33.3 % truncated traces)</li><li>Java Thread Park (0.223 % truncated traces)</li></ul></longDescription>
3151 </rule>
3152 <rule>
3153 <id>StringDeduplication</id>
3154 <severity>OK</severity>
3155 <score>11.944505390960535</score>
3156 <shortDescription>Approximately 17 % of the live set consists of the internal array type of strings ('char[]' for this JDK version).
3157 The heap is around 22 % full. There is likely no big benefit from enabling string deduplication.</shortDescription>
3158 <longDescription>Approximately 17 % of the live set consists of the internal array type of strings ('char[]' for this JDK version).
3159 The heap is around 22 % full. There is likely no big benefit from enabling string deduplication.<p>String deduplication is enabled using the JVM flag '-XX:+UseStringDeduplication'. This flag can be used together with the G1 garbage collector in JDK 8u20 or later.<p>To validate if this gives a performance improvement for your application, create flight recordings both with and without string deduplication. For the run with string deduplication enabled, also enable statistics with '-XX:+PrintStringDeduplicationStatistics' for JDK 8 or '-Xlog:stringdedup*=debug' for JDK 9. Check if the heap live set decrease in the recording with string deduplication enabled is larger than the size of the string deduplication metadata table. The size of the metadata table is printed in the statistics output as 'Table/Memory Usage: XX MB'<p>You can read more about string deduplication in the java options documentation or in <a href="http://openjdk.java.net/jeps/192">JEP 192</a>.<p>String deduplication is only supported when using the G1 garbage collector. If you want to use this feature you can enable G1 by using '-XX:+UseG1GC'.</longDescription>
3160 </rule>
3161 <rule>
3162 <id>SystemGc</id>
3163 <severity>OK</severity>
3164 <score>0.0</score>
3165 <shortDescription>No garbage collections were caused by System.gc().</shortDescription>
3166 <longDescription>No garbage collections were caused by System.gc().</longDescription>
3167 </rule>
3168 <rule>
3169 <id>TlabAllocationRatio</id>
3170 <severity>OK</severity>
3171 <score>3.561374583830773</score>
3172 <shortDescription>The program allocated 2.39 % of the memory outside of TLABs.</shortDescription>
3173 <longDescription>The program allocated 2.39 % of the memory outside of TLABs.</longDescription>
3174 </rule>
3175 <rule>
3176 <id>VMOperations</id>
3177 <severity>OK</severity>
3178 <score>14.8241342</score>
3179 <shortDescription>No excessively long VM operations were found in this recording (the longest was 592.965 ms).</shortDescription>
3180 <longDescription>No excessively long VM operations were found in this recording (the longest was 592.965 ms).</longDescription>
3181 </rule>
3182 <rule>
3183 <id>biasedLockingRevocation</id>
3184 <severity>Not Applicable</severity>
3185 <score>-1.0</score>
3186 <shortDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.</shortDescription>
3187 <longDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.<p>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>
3188 </rule>
3189 <rule>
3190 <id>biasedLockingRevocationPause</id>
3191 <severity>OK</severity>
3192 <score>0.0</score>
3193 <shortDescription>No revocation of biased locks found.</shortDescription>
3194 <longDescription>No revocation of biased locks found.</longDescription>
3195 </rule>
3196 </report>
3197 <report>
3198 <file>wls-medrec-jdk9.jfr</file>
3199 <rule>
3200 <id>Allocations.class</id>
3201 <severity>Not Applicable</severity>
3202 <score>-1.0</score>
3203 <shortDescription>This rule requires events to be available from one of the following event types: jdk.ObjectAllocationInNewTLAB, jdk.ObjectAllocationOutsideTLAB.</shortDescription>
3204 <longDescription>This rule requires events to be available from one of the following event types: jdk.ObjectAllocationInNewTLAB, jdk.ObjectAllocationOutsideTLAB.</longDescription>
3205 </rule>
3206 <rule>
3207 <id>Allocations.thread</id>
3208 <severity>Not Applicable</severity>
3209 <score>-1.0</score>
3210 <shortDescription>This rule requires events to be available from one of the following event types: jdk.ObjectAllocationInNewTLAB, jdk.ObjectAllocationOutsideTLAB.</shortDescription>
3211 <longDescription>This rule requires events to be available from one of the following event types: jdk.ObjectAllocationInNewTLAB, jdk.ObjectAllocationOutsideTLAB.</longDescription>
3212 </rule>
3213 <rule>
3214 <id>ApplicationHalts</id>
3215 <severity>Not Applicable</severity>
3216 <score>-1.0</score>
3217 <shortDescription>This rule requires events to be available from the following event types: 'GC Phase Pause', 'VM Operation'.</shortDescription>
3218 <longDescription>The Application Halts rule requires events to be available from the following event types: 'GC Phase Pause', 'VM Operation'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3219 </rule>
3220 <rule>
3221 <id>BufferLost</id>
3222 <severity>OK</severity>
3223 <score>0.0</score>
3224 <shortDescription>No Flight Recorder buffers were lost during the recording.</shortDescription>
3225 <longDescription>No Flight Recorder buffers were lost during the recording.</longDescription>
3226 </rule>
3227 <rule>
3228 <id>BytecodeVerification</id>
3229 <severity>OK</severity>
3230 <score>0.0</score>
3231 <shortDescription>The application was running with bytecode verification enabled.</shortDescription>
3232 <longDescription>The application was running with bytecode verification enabled.</longDescription>
3233 </rule>
3234 <rule>
3235 <id>ClassLeak</id>
3236 <severity>OK</severity>
3237 <score>0.0</score>
3238 <shortDescription>No classes with identical names have been loaded more times than the limit.</shortDescription>
3239 <longDescription>No classes with identical names have been loaded more times than the limit.</longDescription>
3240 </rule>
3241 <rule>
3242 <id>ClassLoading</id>
3243 <severity>OK</severity>
3244 <score>0.0</score>
3245 <shortDescription>No significant time was spent loading new classes during this recording.</shortDescription>
3246 <longDescription>No significant time was spent loading new classes during this recording.</longDescription>
3247 </rule>
3248 <rule>
3249 <id>CodeCache</id>
3250 <severity>Not Applicable</severity>
3251 <score>-1.0</score>
3252 <shortDescription>This rule requires events to be available from the following event types: 'Code Cache Configuration', 'Code Cache Full', 'Code Cache Statistics', 'JVM Information'.</shortDescription>
3253 <longDescription>The Code Cache rule requires events to be available from the following event types: 'Code Cache Configuration', 'Code Cache Full', 'Code Cache Statistics', 'JVM Information'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3254 </rule>
3255 <rule>
3256 <id>CompareCpu</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: 'CPU Load'.</shortDescription>
3260 <longDescription>The Competing CPU Usage rule requires events to be available from the following event types: 'CPU Load'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3261 </rule>
3262 <rule>
3263 <id>CompressedOops</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: 'Boolean Flag', 'JVM Information', 'Unsigned Long Flag'.</shortDescription>
3267 <longDescription>The Compressed Oops rule requires events to be available from the following event types: 'Boolean Flag', 'JVM Information', 'Unsigned Long Flag'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3268 </rule>
3269 <rule>
3270 <id>ContextSwitch</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: 'Thread Context Switch Rate'.</shortDescription>
3274 <longDescription>The Context Switches rule requires events to be available from the following event types: 'Thread Context Switch Rate'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3275 </rule>
3276 <rule>
3277 <id>DMSIncident</id>
3278 <severity>Not Applicable</severity>
3279 <score>-1.0</score>
3280 <shortDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.</shortDescription>
3281 <longDescription>The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.<p>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>
3282 </rule>
3283 <rule>
3284 <id>DebugNonSafepoints</id>
3285 <severity>OK</severity>
3286 <score>0.0</score>
3287 <shortDescription>DebugNonSafepoints was implicitly enabled in the JVM version used to create this recording.</shortDescription>
3288 <longDescription>DebugNonSafepoints was implicitly enabled in the JVM version used to create this recording.</longDescription>
3289 </rule>
3290 <rule>
3291 <id>DiscouragedVmOptions</id>
3292 <severity>OK</severity>
3293 <score>0.0</score>
3294 <shortDescription>No problems were found with the VM options.</shortDescription>
3295 <longDescription>No problems were found with the VM options.</longDescription>
3296 </rule>
3297 <rule>
3298 <id>DumpReason</id>
3299 <severity>OK</severity>
3300 <score>0.0</score>
3301 <shortDescription>This recording was not dumped for an exceptional reason.</shortDescription>
3302 <longDescription>This recording was not dumped for an exceptional reason.</longDescription>
3303 </rule>
3304 <rule>
3305 <id>DuplicateFlags</id>
3306 <severity>Information</severity>
3307 <score>50.0</score>
3308 <shortDescription>There were 5 JVM duplicated flags.</shortDescription>
3309 <longDescription>There were 5 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: <ul><li>-XX:NewSize=65m, -XX:NewSize=65m</li><li>-Dweblogic.home=C:\weblogic\src122130_build\Oracle_Home\wlserver/server, -Dweblogic.home=C:\weblogic\SRC122~1\ORACLE~1\wlserver\server</li><li>-Xmx500m, -Xmx500m</li><li>-Xms160m, -Xms160m</li><li>-XX:MaxNewSize=65m, -XX:MaxNewSize=65m</li></ul></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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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'.<p>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'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</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>
3351 <longDescription>The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3352 </rule>
3353 <rule>
3354 <id>FlightRecordingSupport</id>
3355 <severity>Warning</severity>
3356 <score>80.0</score>
3357 <shortDescription>The recording is from an early access build.</shortDescription>
3358 <longDescription>This recording is from an early access build of the JRE (Java HotSpot(TM) 64-Bit Server VM (9-ea+148) for windows-amd64 JRE (9-ea+148), built on Dec 7 2016 18:47:38 by "javare" with MS VC++ 12.0 (VS2013)). The automated analysis is not supported, and you may see errors when attempting to analyze the recording.</longDescription>
3359 </rule>
3360 <rule>
3361 <id>GcFreedRatio</id>
3362 <severity>Not Applicable</severity>
3363 <score>-1.0</score>
3364 <shortDescription>This rule requires events to be available from the following event types: 'Heap Summary'.</shortDescription>
3365 <longDescription>The GC Freed Ratio rule requires events to be available from the following event types: 'Heap Summary'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3366 </rule>
3367 <rule>
3368 <id>GcLocker</id>
3369 <severity>OK</severity>
3370 <score>0.0</score>
3371 <shortDescription>The GC Locker did not cause any garbage collections.</shortDescription>
3372 <longDescription>The GC Locker did not cause any garbage collections.</longDescription>
3373 </rule>
3374 <rule>
3375 <id>GcOptions</id>
3376 <severity>Not Applicable</severity>
3377 <score>-1.0</score>
3378 <shortDescription>Too few events to calculate the result.</shortDescription>
3379 <longDescription>Too few events to calculate the result.</longDescription>
3380 </rule>
3381 <rule>
3382 <id>GcPauseRatio</id>
3383 <severity>Not Applicable</severity>
3384 <score>-1.0</score>
3385 <shortDescription>This rule requires events to be available from the following event types: 'GC Phase Pause'.</shortDescription>
3386 <longDescription>The GC Pauses rule requires events to be available from the following event types: 'GC Phase Pause'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3387 </rule>
3388 <rule>
3389 <id>GcStall</id>
3390 <severity>Not Applicable</severity>
3391 <score>-1.0</score>
3392 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
3393 <longDescription>The GC Stall rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3394 </rule>
3395 <rule>
3396 <id>HeapContent</id>
3397 <severity>Not Applicable</severity>
3398 <score>-1.0</score>
3399 <shortDescription>This rule requires events to be available from the following event types: 'Object Count'.</shortDescription>
3400 <longDescription>The Heap Content rule requires events to be available from the following event types: 'Object Count'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3401 </rule>
3402 <rule>
3403 <id>HeapInspectionGc</id>
3404 <severity>Not Applicable</severity>
3405 <score>-1.0</score>
3406 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
3407 <longDescription>The GCs Caused by Heap Inspection rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3408 </rule>
3409 <rule>
3410 <id>HighGc</id>
3411 <severity>OK</severity>
3412 <score>0.0</score>
3413 <shortDescription>The runtime did not spend much time performing garbage collections.</shortDescription>
3414 <longDescription>The runtime did not spend much time performing garbage collections.</longDescription>
3415 </rule>
3416 <rule>
3417 <id>HighJvmCpu</id>
3418 <severity>Not Applicable</severity>
3419 <score>-1.0</score>
3420 <shortDescription>This rule requires events to be available from the following event types: 'CPU Load'.</shortDescription>
3421 <longDescription>The High JVM CPU Load rule requires events to be available from the following event types: 'CPU Load'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3422 </rule>
3423 <rule>
3424 <id>IncreasingLiveSet</id>
3425 <severity>Not Applicable</severity>
3426 <score>-1.0</score>
3427 <shortDescription>Too few events to calculate the result.</shortDescription>
3428 <longDescription>Too few events to calculate the result.</longDescription>
3429 </rule>
3430 <rule>
3431 <id>IncreasingMetaSpaceLiveSet</id>
3432 <severity>OK</severity>
3433 <score>0.0</score>
3434 <shortDescription>The class data does not seem to increase during the recording.</shortDescription>
3435 <longDescription>The class data does not seem to increase during the recording.</longDescription>
3436 </rule>
3437 <rule>
3438 <id>JavaBlocking</id>
3439 <severity>Not Applicable</severity>
3440 <score>-1.0</score>
3441 <shortDescription>This rule requires events to be available from the following event types: 'Java Monitor Blocked'.</shortDescription>
3442 <longDescription>The Java Blocking rule requires events to be available from the following event types: 'Java Monitor Blocked'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3443 </rule>
3444 <rule>
3445 <id>LongGcPause</id>
3446 <severity>OK</severity>
3447 <score>0.0</score>
3448 <shortDescription>The application did not cause any long GC pause times.</shortDescription>
3449 <longDescription>The application did not cause any long GC pause times.</longDescription>
3450 </rule>
3451 <rule>
3452 <id>LowOnPhysicalMemory</id>
3453 <severity>Not Applicable</severity>
3454 <score>-1.0</score>
3455 <shortDescription>This rule requires events to be available from the following event types: 'Physical Memory'.</shortDescription>
3456 <longDescription>The Free Physical Memory rule requires events to be available from the following event types: 'Physical Memory'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3457 </rule>
3458 <rule>
3459 <id>ManagementAgent</id>
3460 <severity>OK</severity>
3461 <score>0.0</score>
3462 <shortDescription>No problems were found with the management agent settings.</shortDescription>
3463 <longDescription>No problems were found with the management agent settings.</longDescription>
3464 </rule>
3465 <rule>
3466 <id>ManyRunningProcesses</id>
3467 <severity>Not Applicable</severity>
3468 <score>-1.0</score>
3469 <shortDescription>This rule requires events to be available from the following event types: 'System Process'.</shortDescription>
3470 <longDescription>The Competing Processes rule requires events to be available from the following event types: 'System Process'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3471 </rule>
3472 <rule>
3473 <id>MetaspaceOom</id>
3474 <severity>OK</severity>
3475 <score>0.0</score>
3476 <shortDescription>The metaspace was not exhausted during this recording.</shortDescription>
3477 <longDescription>The metaspace was not exhausted during this recording.</longDescription>
3478 </rule>
3479 <rule>
3480 <id>MethodProfiling</id>
3481 <severity>Not Applicable</severity>
3482 <score>-1.0</score>
3483 <shortDescription>This rule requires events to be available from the following event types: 'Method Profiling Sample', 'Recording Setting'.</shortDescription>
3484 <longDescription>The Method Profiling rule requires events to be available from the following event types: 'Method Profiling Sample', 'Recording Setting'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3485 </rule>
3486 <rule>
3487 <id>Options</id>
3488 <severity>OK</severity>
3489 <score>0.0</score>
3490 <shortDescription>No undocumented, deprecated or non-recommended option flags were detected.</shortDescription>
3491 <longDescription>No undocumented, deprecated or non-recommended option flags were detected.</longDescription>
3492 </rule>
3493 <rule>
3494 <id>OverAggressiveRecordingSetting</id>
3495 <severity>Information</severity>
3496 <score>50.0</score>
3497 <shortDescription>These following event types had no threshold: &#39;Java Monitor Blocked&#39;, &#39;Java Thread Park&#39;.</shortDescription>
3498 <longDescription>Event types without threshold can lead to quite a lot of events being generated, possibly translating to higher overhead. If this was not intended, please check the settings in the template for future recordings.</longDescription>
3499 </rule>
3500 <rule>
3501 <id>PasswordsInArguments</id>
3502 <severity>OK</severity>
3503 <score>0.0</score>
3504 <shortDescription>The recording does not seem to contain passwords in the application arguments.</shortDescription>
3505 <longDescription>The recording does not seem to contain passwords in the application arguments.</longDescription>
3506 </rule>
3507 <rule>
3508 <id>PasswordsInEnvironment</id>
3509 <severity>Not Applicable</severity>
3510 <score>-1.0</score>
3511 <shortDescription>This rule requires events to be available from the following event types: 'Initial Environment Variable'.</shortDescription>
3512 <longDescription>The Passwords in Environment Variables rule requires events to be available from the following event types: 'Initial Environment Variable'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3513 </rule>
3514 <rule>
3515 <id>PasswordsInSystemProperties</id>
3516 <severity>Not Applicable</severity>
3517 <score>-1.0</score>
3518 <shortDescription>This rule requires events to be available from the following event types: 'Initial System Property'.</shortDescription>
3519 <longDescription>The Passwords in System Properties rule requires events to be available from the following event types: 'Initial System Property'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3520 </rule>
3521 <rule>
3522 <id>PrimitiveToObjectConversion</id>
3523 <severity>Not Applicable</severity>
3524 <score>-1.0</score>
3525 <shortDescription>This rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
3526 <longDescription>The Primitive To Object Conversion rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3527 </rule>
3528 <rule>
3529 <id>SocketRead</id>
3530 <severity>Not Applicable</severity>
3531 <score>-1.0</score>
3532 <shortDescription>This rule requires events to be available from the following event types: 'Socket Read'.</shortDescription>
3533 <longDescription>The Socket Read Peak Duration rule requires events to be available from the following event types: 'Socket Read'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3534 </rule>
3535 <rule>
3536 <id>SocketWrite</id>
3537 <severity>Not Applicable</severity>
3538 <score>-1.0</score>
3539 <shortDescription>This rule requires events to be available from the following event types: 'Socket Write'.</shortDescription>
3540 <longDescription>The Socket Write Peak Duration rule requires events to be available from the following event types: 'Socket Write'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3541 </rule>
3542 <rule>
3543 <id>StackdepthSetting</id>
3544 <severity>Warning</severity>
3545 <score>99.35136572520041</score>
3546 <shortDescription>Some stack traces were truncated in this recording.</shortDescription>
3547 <longDescription>Some stack traces were truncated in this recording.<p>The Flight Recorder only records traces with a depth up to the maximum stack depth value set to 64. This is the default depth. 17.5 % of all traces were larger than this option, and were therefore truncated. If more detailed traces are required, increase the '-XX:FlightRecorderOptions=stackdepth=&lt;value&gt;' value.<p>Events of the following types have truncated stack traces:<ul><li>EJB Pool Manager Pre Invoke (71.3 % truncated traces)</li><li>EJB Business Method Invoke (71.3 % truncated traces)</li><li>EJB Business Method Post Invoke Cleanup (71.3 % truncated traces)</li><li>EJB Pool Manager Post Invoke (71.3 % truncated traces)</li><li>EJB Business Method Post Invoke (71.3 % truncated traces)</li><li>EJB Business Method Pre Invoke (71.3 % truncated traces)</li><li>JDBC Connection Close (96.8 % truncated traces)</li><li>JDBC Statement Creation (100 % truncated traces)</li><li>JDBC Connection Prepare (100 % truncated traces)</li><li>JDBC Statement Execute (96.7 % truncated traces)</li><li>JDBC Statement Execute Begin (96.7 % truncated traces)</li><li>JTA Transaction Start (16.7 % truncated traces)</li><li>JDBC Transaction Start (100 % truncated traces)</li><li>EJB Pool Manager Create (75 % truncated traces)</li><li>JDBC Connection Release (85.7 % truncated traces)</li><li>Debug (1.59 % truncated traces)</li><li>JDBC Transaction Commit (45 % truncated traces)</li><li>JDBC Transaction End (45 % truncated traces)</li><li>JTA Transaction End (6.06 % truncated traces)</li><li>JTA Transaction Commit (36.4 % truncated traces)</li><li>JDBC Transaction Is Same RM (1.79 % truncated traces)</li><li>Webservices JAXWS Resource (50 % truncated traces)</li><li>Webservices JAXWS Endpoint (100 % truncated traces)</li><li>Servlet Response Write Headers (1.87 % truncated traces)</li><li>Webservices JAXRPC Client Request (50 % truncated traces)</li><li>Webservices JAXRPC Client Response (100 % truncated traces)</li></ul></longDescription>
3548 </rule>
3549 <rule>
3550 <id>StringDeduplication</id>
3551 <severity>Not Applicable</severity>
3552 <score>-1.0</score>
3553 <shortDescription>This rule requires events to be available from the following event types: 'Heap Summary'.</shortDescription>
3554 <longDescription>The String Deduplication rule requires events to be available from the following event types: 'Heap Summary'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3555 </rule>
3556 <rule>
3557 <id>SystemGc</id>
3558 <severity>Not Applicable</severity>
3559 <score>-1.0</score>
3560 <shortDescription>This rule requires events to be available from the following event types: 'Garbage Collection'.</shortDescription>
3561 <longDescription>The GCs Caused by System.gc() rule requires events to be available from the following event types: 'Garbage Collection'.<p>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 <a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html">-XX:FlightRecorderOptions</a>.</longDescription>
3562 </rule>
3563 <rule>
3564 <id>TlabAllocationRatio</id>
3565 <severity>OK</severity>
3566 <score>0.0</score>
3567 <shortDescription>No object allocations outside of TLABs detected.</shortDescription>
3568 <longDescription>No object allocations outside of TLABs detected.</longDescription>
3569 </rule>
3570 <rule>
3571 <id>VMOperations</id>
3572 <severity>OK</severity>
3573 <score>0.0</score>
3574 <shortDescription>No excessively long VM operations were found in this recording (the longest was 0 s).</shortDescription>
3575 <longDescription>No excessively long VM operations were found in this recording (the longest was 0 s).</longDescription>
3576 </rule>
3577 <rule>
3578 <id>biasedLockingRevocation</id>
3579 <severity>Not Applicable</severity>
3580 <score>-1.0</score>
3581 <shortDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.</shortDescription>
3582 <longDescription>The Biased Locking Revocation rule requires the following event types: 'jdk.BiasedLockClassRevocation'.<p>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>
3583 </rule>
3584 <rule>
3585 <id>biasedLockingRevocationPause</id>
3586 <severity>OK</severity>
3587 <score>0.0</score>
3588 <shortDescription>No revocation of biased locks found.</shortDescription>
3589 <longDescription>No revocation of biased locks found.</longDescription>
3590 </rule>
3591 </report>
3592 </reportcollection>