< prev index next >

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

Print this page




3127 <id>biasedLockingRevocation</id>
3128 <severity>Not Applicable</severity>
3129 <score>-1.0</score>
3130 <shortDescription>The Biased Locking Revocation rule requires the following event types: 'com.oracle.jdk.BiasedLockClassRevocation'.</shortDescription>
3131 <longDescription>The Biased Locking Revocation rule requires the following event types: 'com.oracle.jdk.BiasedLockClassRevocation'.&lt;p&gt;They are either not available in this version of Java, or must be enabled in a third-party component. If you are using an older Java version, then you can consider upgrading.</longDescription>
3132 </rule>
3133 <rule>
3134 <id>biasedLockingRevocationPause</id>
3135 <severity>OK</severity>
3136 <score>0.0</score>
3137 <shortDescription>No revocation of biased locks found.</shortDescription>
3138 <longDescription>No revocation of biased locks found.</longDescription>
3139 </rule>
3140 </report>
3141 <report>
3142 <file>wls-medrec-jdk9.jfr</file>
3143 <rule>
3144 <id>Allocations.class</id>
3145 <severity>Not Applicable</severity>
3146 <score>-1.0</score>
3147 <shortDescription>This rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
3148 <longDescription>The Allocated Classes rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.&lt;p&gt;They were either disabled during the recording or there might not have happened anything to trigger an event. Event settings like period and threshold may also prevent some events from being emitted. If you are using JMC to create a flight recording, then you can enable and configure event types in the Start Flight Recording wizard. If you are starting the flight recording from the command line, then you can use the settings parameter of &lt;a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html"&gt;-XX:FlightRecorderOptions&lt;/a&gt;.</longDescription>
3149 </rule>
3150 <rule>
3151 <id>Allocations.thread</id>
3152 <severity>Not Applicable</severity>
3153 <score>-1.0</score>
3154 <shortDescription>This rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.</shortDescription>
3155 <longDescription>The Threads Allocating rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.&lt;p&gt;They were either disabled during the recording or there might not have happened anything to trigger an event. Event settings like period and threshold may also prevent some events from being emitted. If you are using JMC to create a flight recording, then you can enable and configure event types in the Start Flight Recording wizard. If you are starting the flight recording from the command line, then you can use the settings parameter of &lt;a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html"&gt;-XX:FlightRecorderOptions&lt;/a&gt;.</longDescription>
3156 </rule>
3157 <rule>
3158 <id>ApplicationHalts</id>
3159 <severity>Not Applicable</severity>
3160 <score>-1.0</score>
3161 <shortDescription>This rule requires events to be available from the following event types: 'GC Phase Pause', 'VM Operation'.</shortDescription>
3162 <longDescription>The Application Halts rule requires events to be available from the following event types: 'GC Phase Pause', 'VM Operation'.&lt;p&gt;They were either disabled during the recording or there might not have happened anything to trigger an event. Event settings like period and threshold may also prevent some events from being emitted. If you are using JMC to create a flight recording, then you can enable and configure event types in the Start Flight Recording wizard. If you are starting the flight recording from the command line, then you can use the settings parameter of &lt;a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html"&gt;-XX:FlightRecorderOptions&lt;/a&gt;.</longDescription>
3163 </rule>
3164 <rule>
3165 <id>BufferLost</id>
3166 <severity>OK</severity>
3167 <score>0.0</score>
3168 <shortDescription>No Flight Recorder buffers were lost during the recording.</shortDescription>
3169 <longDescription>No Flight Recorder buffers were lost during the recording.</longDescription>
3170 </rule>
3171 <rule>
3172 <id>BytecodeVerification</id>
3173 <severity>OK</severity>
3174 <score>0.0</score>
3175 <shortDescription>The application was running with bytecode verification enabled.</shortDescription>




3127 <id>biasedLockingRevocation</id>
3128 <severity>Not Applicable</severity>
3129 <score>-1.0</score>
3130 <shortDescription>The Biased Locking Revocation rule requires the following event types: 'com.oracle.jdk.BiasedLockClassRevocation'.</shortDescription>
3131 <longDescription>The Biased Locking Revocation rule requires the following event types: 'com.oracle.jdk.BiasedLockClassRevocation'.&lt;p&gt;They are either not available in this version of Java, or must be enabled in a third-party component. If you are using an older Java version, then you can consider upgrading.</longDescription>
3132 </rule>
3133 <rule>
3134 <id>biasedLockingRevocationPause</id>
3135 <severity>OK</severity>
3136 <score>0.0</score>
3137 <shortDescription>No revocation of biased locks found.</shortDescription>
3138 <longDescription>No revocation of biased locks found.</longDescription>
3139 </rule>
3140 </report>
3141 <report>
3142 <file>wls-medrec-jdk9.jfr</file>
3143 <rule>
3144 <id>Allocations.class</id>
3145 <severity>Not Applicable</severity>
3146 <score>-1.0</score>
3147 <shortDescription>This rule requires events to be available from one of the following event types: com.oracle.jdk.ObjectAllocationInNewTLAB, com.oracle.jdk.ObjectAllocationOutsideTLAB.</shortDescription>
3148 <longDescription>This rule requires events to be available from one of the following event types: com.oracle.jdk.ObjectAllocationInNewTLAB, com.oracle.jdk.ObjectAllocationOutsideTLAB.</longDescription>
3149 </rule>
3150 <rule>
3151 <id>Allocations.thread</id>
3152 <severity>Not Applicable</severity>
3153 <score>-1.0</score>
3154 <shortDescription>This rule requires events to be available from one of the following event types: com.oracle.jdk.ObjectAllocationInNewTLAB, com.oracle.jdk.ObjectAllocationOutsideTLAB.</shortDescription>
3155 <longDescription>This rule requires events to be available from one of the following event types: com.oracle.jdk.ObjectAllocationInNewTLAB, com.oracle.jdk.ObjectAllocationOutsideTLAB.</longDescription>
3156 </rule>
3157 <rule>
3158 <id>ApplicationHalts</id>
3159 <severity>Not Applicable</severity>
3160 <score>-1.0</score>
3161 <shortDescription>This rule requires events to be available from the following event types: 'GC Phase Pause', 'VM Operation'.</shortDescription>
3162 <longDescription>The Application Halts rule requires events to be available from the following event types: 'GC Phase Pause', 'VM Operation'.&lt;p&gt;They were either disabled during the recording or there might not have happened anything to trigger an event. Event settings like period and threshold may also prevent some events from being emitted. If you are using JMC to create a flight recording, then you can enable and configure event types in the Start Flight Recording wizard. If you are starting the flight recording from the command line, then you can use the settings parameter of &lt;a href="https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html"&gt;-XX:FlightRecorderOptions&lt;/a&gt;.</longDescription>
3163 </rule>
3164 <rule>
3165 <id>BufferLost</id>
3166 <severity>OK</severity>
3167 <score>0.0</score>
3168 <shortDescription>No Flight Recorder buffers were lost during the recording.</shortDescription>
3169 <longDescription>No Flight Recorder buffers were lost during the recording.</longDescription>
3170 </rule>
3171 <rule>
3172 <id>BytecodeVerification</id>
3173 <severity>OK</severity>
3174 <score>0.0</score>
3175 <shortDescription>The application was running with bytecode verification enabled.</shortDescription>


< prev index next >