Automated Analysis Result Overview

Java Application

N/A

Threads Allocating

This rule requires events to be available from one of the following event types: jdk.ObjectAllocationInNewTLAB, jdk.ObjectAllocationOutsideTLAB.

N/A

Application Halts

This rule requires events to be available from the following event types: 'GC Phase Pause', 'VM Operation'.

The Application Halts rule requires events to be available from the following event types: 'GC Phase Pause', 'VM Operation'.

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 -XX:FlightRecorderOptions.

Parallel Threads

The application seems to be idle. Max average JVM CPU usage was 0.091 % during a 10 s time window starting at 2021-11-18, 4:39:43 p.m..

This may be caused by application latencies, see information from other rules, or it could be that the application is not doing anything.

High JVM CPU Load

The JVM does not seem to cause a lot of CPU load.

Memory

N/A

Allocated Classes

This rule requires events to be available from one of the following event types: jdk.ObjectAllocationInNewTLAB, jdk.ObjectAllocationOutsideTLAB.

N/A

GC Freed Ratio

This rule requires events to be available from the following event types: 'Heap Summary'.

The GC Freed Ratio rule requires events to be available from the following event types: 'Heap Summary'.

N/A

Heap Content

This rule requires events to be available from the following event types: 'Object Count'.

The Heap Content rule requires events to be available from the following event types: 'Object Count'.

GC Pressure

The runtime did not spend much time performing garbage collections.

Free Physical Memory

The system did not run low on physical memory during this recording.

N/A

Primitive To Object Conversion

This rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.

The Primitive To Object Conversion rule requires events to be available from the following event types: 'Allocation in new TLAB', 'Allocation outside TLAB'.

N/A

String Deduplication

This rule requires events to be available from the following event types: 'Heap Summary'.

The String Deduplication rule requires events to be available from the following event types: 'Heap Summary'.

Lock Instances

N/A

Context Switches

Too few events to calculate the result.

Java Blocking

No excessive problems with lock contention found.

The following regular expression was used to exclude threads from this rule: '(.*weblogic\.socket\.Muxer.*)'

File I/O

File Read Peak Duration

There are no file read events in this recording.

N/A

File Write Peak Duration

This rule requires events to be available from the following event types: 'File Write'.

The File Write Peak Duration rule requires events to be available from the following event types: 'File Write'.

Socket I/O

Socket Read Peak Duration

No long socket read pauses were found in this recording (the longest was 202.108 ms).

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.

N/A

Socket Write Peak Duration

This rule requires events to be available from the following event types: 'Socket Write'.

The Socket Write Peak Duration rule requires events to be available from the following event types: 'Socket Write'.

Method Profiling

No methods where optimization would be particularly efficient could be detected.

Exceptions

Thrown Errors

The program generated an average of 3 errors per minute during 2021-11-18, 4:40:04 p.m. – 4:41:04 p.m..

The program generated an average of 3 errors per minute during 2021-11-18, 4:40:04 p.m. – 4:41:04 p.m., 3 errors were thrown in total.

The most common error was 'java.lang.NoSuchMethodError', which was thrown 3 times.

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.

Thrown Exceptions

The program generated 50.6 exceptions per second during 1.007 s starting at 2021-11-18, 4:40:22 p.m..

JVM Internals

Bytecode Verification

The application was running with bytecode verification enabled.

DebugNonSafepoints

DebugNonSafepoints was implicitly enabled in the JVM version used to create this recording.

Discouraged VM Options

No problems were found with the VM options.

Duplicated Flags

There were no duplicate JVM flags on the command line.

N/A

Fatal Errors

This rule requires events to be available from the following event types: 'JVM Shutdown'.

The Fatal Errors rule requires events to be available from the following event types: 'JVM Shutdown'.

Flight Recording Support

The JVM version used for this recording has full Flight Recorder support.

GC Setup

No problems were found with the GC configuration.

Discouraged Management Agent Settings

No problems were found with the management agent settings.

Command Line Options Check

No undocumented, deprecated or non-recommended option flags were detected.

Passwords in Java Arguments

The recording does not seem to contain passwords in the application arguments.

Stackdepth Setting

Some stack traces were truncated in this recording.

The Flight Recorder only records traces with a depth up to the maximum stack depth value set to 64. This is the default depth. 0.0316 % of all traces were larger than this option, and were therefore truncated. If more detailed traces are required, increase the '-XX:FlightRecorderOptions=stackdepth=<value>' value.

Events of the following types have truncated stack traces:

Method Profiling Sample (8 % truncated traces)

Garbage Collections

N/A

G1/CMS Full Collection

This rule requires events to be available from the following event types: 'Garbage Collection'.

The G1/CMS Full Collection rule requires events to be available from the following event types: 'Garbage Collection'.

GCs Caused by GC Locker

No GCs were affected by the GC Locker.

N/A

GC Pauses

This rule requires events to be available from the following event types: 'GC Phase Pause'.

The GC Pauses rule requires events to be available from the following event types: 'GC Phase Pause'.

N/A

GC Stall

This rule requires events to be available from the following event types: 'Garbage Collection'.

The GC Stall rule requires events to be available from the following event types: 'Garbage Collection'.

N/A

GCs Caused by Heap Inspection

This rule requires events to be available from the following event types: 'Garbage Collection'.

The GCs Caused by Heap Inspection rule requires events to be available from the following event types: 'Garbage Collection'.

Metaspace Live Set Trend

The class data does not seem to increase during the recording.

GC Pause Peak Duration

The application did not cause any long GC pause times.

Metaspace Out of Memory

The metaspace was not exhausted during this recording.

N/A

GCs Caused by System.gc()

This rule requires events to be available from the following event types: 'Garbage Collection'.

The GCs Caused by System.gc() rule requires events to be available from the following event types: 'Garbage Collection'.

GC Configuration

Compressed Oops

The settings for Compressed Oops were OK.

Compilations

Code Cache

N/A

Code Cache

This rule requires events to be available from the following event types: 'Code Cache Configuration', 'Code Cache Full', 'Code Cache Statistics', 'JVM Information'.

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'.

Class Loading

Class Leak

No classes with identical names have been loaded more times than the limit.

Class Loading Pressure

No significant time was spent loading new classes during this recording.

VM Operations

VMOperation Peak Duration

No excessively long VM operations were found in this recording (the longest was 128.768 ms).

Biased Locking Revocation Pauses

No revocation of biased locks found.

TLAB Allocations

TLAB Allocation Ratio

No object allocations outside of TLABs detected.

Environment

Processes

Competing CPU Ratio Usage

An average CPU load of 4 % was caused by other processes during 1.010 s starting at 2021-11-18, 4:41:06 p.m..

Competing Processes

1 processes were running while this Flight Recording was made.

At 2021-11-18, 4:40:08 p.m., a total of 1 other processes were running on the host machine that this Flight Recording was made on.

Environment Variables

Passwords in Environment Variables

The recording does not seem to contain passwords in the environment variables.

System Properties

100

Passwords in System Properties

The system properties in the recording may contain passwords.

The following suspicious system properties were found in this recording:

javax.net.ssl.keyStorePassword
javax.net.ssl.trustStorePassword
com.sun.management.jmxremote.password.file

They may contain passwords. If you wish to keep having passwords in your system properties, but want to be able to share recordings without also sharing the passwords, please disable the 'Initial System Property' event.

Recording

Lost Flight Recorder Buffers

No Flight Recorder buffers were lost during the recording.

Exceptional Dump Reason

This recording was not dumped for an exceptional reason.

Discouraged Recording Settings

No problems were found with the recording settings.

Event Browser

N/A

DMS Incidents

The DMS Incidents rule requires the following event types: 'http://www.oracle.com/dms/dfw/dms/dfw/DFW_Incident/DFW_Incident_state'.

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.

N/A

Heap Live Set Trend

Too few events to calculate the result.

Biased Locking Revocation

Fully revoked classes found. Instances of classes were revoked more times than the user configured limit.

The following classes were disabled from using biased locking:

io.grpc.netty.shaded.io.netty.channel.DefaultChannelPromise

The following instances of classes were revoked more than the user configured limit for this rule (limit=15, not including disabled classes):

java.util.Vector (28)
javax.management.NotificationFilterSupport (28)
javax.management.ObjectName (24)
java.lang.Thread (16)

Biased locking is a technique used by the JVM to decrease the cost of uncontended locking to near lock free performance. A thread can bias a lock object to itself, making subsequent locking by the same thread very inexpensive. If the lock starts being used by other threads, the bias can either be revoked, rebiased towards the other thread, or revoked from being biased again for the rest of the runtime of the JVM.

Having a lot of revoked classes need not be a problem, but can provide opportunities for optimizations, tuning and design improvements. For example, if you have a lot of contention during the startup of your application, the revocation costs may be significant, and you may want to delay the enablement of biased locking using the '-XX:BiasedLockingStartupDelay=<time in ms>' flag. For applications that heavily depend on contended locking, and cannot be redesigned, it may be beneficial to turn off biased locking altogether ('-XX:-UseBiasedLocking'). For benchmarking, you may want to set '-XX:BiasedLockingStartupDelay' to zero.

The following classes were filtered out: [java.lang.ref.ReferenceQueue$Lock]

WebLogic