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>
|
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>0.8005001984324781</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>
|