Exceptions, Errors, and Other Messages

Select the exception or error message you have from the list below.

AttachNotSupportedException: Unable to open socket file: target process not responding or HotSpot VM not loaded

This error is thrown when attempting to use any tools that use the Attach API to attach to a running Java process but the target JVM’s socket file is missing.

Could not derive key -or- Could not decrypt key

Either of these errors may be seen after applying the October 2022 CPU.

Expired X.509 Certificates

Messages about expired X.509 certificates can take a variety of forms.

Failed to reserve large pages memory req_addr: 0x0000000080000000 bytes: <NNNNNNNNNN> (errno = 12)

This error is thrown when the HugePage area is smaller than JavaVM needs.

A fatal error has been detected by the Java Runtime Environment: SIGSEGV (0xb) at pc=0xffffffff7ea8241c, pid=<PID>, tid=<TID> -or- SIGBUS (0x7) at pc=0x00007f34165d4d10, pid=<PID>, tid=<TID>

These errors may appear in the HotSpot Fatal Error Log or application log after a crash. They are caused by the .jar files of the application, or the JDK itself, being overwritten while the application is running.

java.lang.IllegalArgumentException -or- javax.naming.NamingException

These errors may be seen after updating to the April 2022 CPU. The cause is an application code issue.

java.lang.OutOfMemoryError

This error will be appended with a detail message. Click through to select your particular message.

javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

Occurs when RSASSA-PSS Signature service is being used in TLS communication with Bouncy Castle FIPS provider (prior to version 1.2.0.3).

keytool error: java.security.UnrecoverableKeyException: Could not decrypt key: Could not decrypt data

The issue is with the JSafeJCE provider support for recently upgraded default PKCS12 encryption algorithm in JDK.

Native memory allocation (mmap) failed to map <NNNNNNN> bytes for committing reserved memory.'

This type of OutOfMemoryError crash can have a few causes.

Security Warning: Certificate from a Non-Trusted Certificate Authority

There are several ways to overcome a security warning if an applet or a JNLP application was signed with a certificate that was obtained from a non-trusted certificate authority.

There Is Insufficient Memory For The Java Runtime Environment To Continue. Cannot create GC thread. Out of system resources.

This message can be thrown on Linux when the maximum number of processes or threads that a user can run has been set too low.

Unable to ensure the certificate used to identify the application has not been revoked.

This message indicates that the X.509 certificate was not issued by a trusted Certificate Authority.