Last updated on NOVEMBER 05, 2016
Applies to:Oracle GlassFish Server - Version 8.1 to 8.2 [Release 8.1 to 8.2]
Oracle GlassFish Server - Version 2.1.1 and later
Information in this document applies to any platform.
This problem can be seen with 8.1 UR2, 8.2 and 9.x/2.x.
GlassFish Server 2.x
This problem can be encountered when installing GlassFish Server from any of the installation bundles that include HADB and specifying a Java JDK 6u37 or higher. By default these installations create an enterprise profile domain in which the Java security manager is enabled to enforce the policies in the domain's server.policy file. The non-HADB installation bundles by default create a developer profile domain in which the security manager is not enabled. The patch numbers associated with the file-based installation bundles that contain HADB are:
It is also possible to encounter this problem by updating the JDK version an installation is using by updating the AS_JAVA value in the <install-dir>/config/asenv.conf file and subsequently attempting to create new instances after restarting the domain administration server (DAS) and node agents (NA). This could equally apply to package based installations, but then it is more likely to be encountered with a change to the JDK being used with an existing installation, rather than being a new installation.
The following error is reported in the node agent's server.log file:
Performing a clean installation of GlassFish Server 2.x with Java JDK 6u37 or higher, or updating an existing installation to use Java JDK 6u37 or higher.
Performing a clean installation of Sun Application Server 8.x with Java JDK 5u38 or higher, or updating an existing installation to use Java JDK 5u38 or higher.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms