[frs-324] License activation is unreliable with Glassfish servers


Background

A standard Glassfish 3.x or 4.0 installation is deployed with a keyStore and no keyStorePassword.

This configuration is not supported by Java.

When FusionReactor attempts to acquire a license it makes a connection to the Intergral license servers via HTTPS. The strange glassfish configuration causes the exception "Password cannot be null" and causes the license request to fail.

The user has to then perform a manual activation.

The issue can affect the auto-activation of the license inside Glassfish and make it a little random. This is dependent on what WebApps (if any) are deployed into Glassfish and the FusionReactor and Glassfish startup order.

Workaround

There are multiple workarounds for this problem:

  • Add the following JVM option to the domain.xml file
    • <jvm-options>-Dfrlicenseservice.protocol=http</jvm-options>
  • Comment out the keyStore line to the domain.xml file
    • <!--<jvm-options>-Djavax.net.ssl.keyStore=${com.sun.aas.instanceRoot}/config/keystore.jks</jvm-options>-->
  • Add the missing default keyStorePassword line to the domain.xml file
    • <jvm-options>-Djavax.net.ssl.keyStorePassword=changeit</jvm-options>

Any one of these solutions fixes the activation of the license.

Issue Details

Type: Technote
Issue Number: FRS-324
Components: License + Activation
Environment:
Resolution: Fixed
Last Updated: 15/Jan/14 12:08 PM
Affects Version: 5.0.0
Fixed Version: 5.0.0
Server: GlassFish
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris, Windows Vista, Windows x64, AIX, Windows 7, Windows 2008
Related Issues: