My Oracle Support Banner

SSLHandshakeException After Changing GlassFish Java_Home to use a Different Java Version from the Installation's Default JDK (Doc ID 2002170.1)

Last updated on SEPTEMBER 13, 2023

Applies to:

Oracle GlassFish Server - Version 2.1.1 to 2.1.1 [Release 2.1]
Information in this document applies to any platform.


The following error is reported by a client after a configuration in the domain has been updated to use a different JDK from the default:

All clusters and standalone instances will be using this JDK.  However, each configuration in the domain (a configuration is created when a cluster or standalone instance is first created) also has a "Java Home" value visible on its "JVM Settings" page.  This will show the JDK home set by AS_JAVA - in the GUI this will show the full path, but in the domain.xml the actual value is ${com.sun.aas.JavaRoot} which is converted by the GUI into the value for AS_JAVA.

The problem occurs when the configuration's "Java Home" value is changed to a different  JDK version from the installation's default, as this leads to any GlassFish instance's using the modified configuration to use a mix of files from both JDKs, as shown in the section above.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.