My Oracle Support Banner

Addressing Glassfish 5.x Admin Console Problems With JDK8 For Convergence Deployment (Doc ID 2855710.1)

Last updated on MARCH 15, 2022

Applies to:

Oracle Communications Convergence - Version 3.0.2 and later
Information in this document applies to any platform.
APPLIES TO:

Convergence 3.0.3.0.0

Oracle GlassFish Server 5.x

Convergence 3.0.3.0.0 and beyond is only supported on Oracle WebLogic Server. Deployments on open source GlassFish application server are enabled, but not supported by Oracle.

Glassfish 5.x and JDK 1.8.X combinations have few known issues when secure admin is enabled in Glassfish and below are the workaround that can be performed when similar issues are seen in order to use Glassfish 5.x as a container for Convergence. Refer to the Table 1.1 - Container Support matrix for Convergence 3.0.3.0.0 - for suggested JDK versions.

Symptoms

When secure-admin is enabled for Glassfish, issues such as the Glassfish domain not starting properly and the asadmin command execution showing errors are noticed irrespective of Convergence being deployed in Glassfish.

The symptoms could be any of the following:

  1.  Convergence is working fine with Glassfish 5.0.1 and JDK 1.8.0_241 but fails to load the application when higher versions of JDK 1.8 is used in the Glassfish Configuration.
    • Glassfish Server log shows: Startup of context /iwc failed due to previous errors 
  2.  With JDK8u251 and above: After executing "asadmin enable-secure-admin" command, the Glassfish domain is not starting successfully. 
    • Glassfish Server log shows:
      •  GRIZZLY0013: Exception during FilterChain execution
         java.lang.NoSuchFieldError: nullSession
  3.  With JDK8u291 and above: After executing "asadmin enable-secure-admin" command, the Glassfish domain is not starting successfully. 
    • Glassfish Server log
      •  Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)

 

Cause

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

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


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