This section addresses issues that can occur during an upgrade to GlassFish Server 3.1.
The following topics are addressed here:
When upgrading a clustered domain configuration from Application Server 9.1 or Enterprise Server v2 to GlassFish Server 3.1, you may encounter problems if the admin-service element in the DAS domain.xml file sets both of the following attributes:
The security-enabled attribute must be set to false in the admin-service element for the DAS when type is set to das-and-server.
You can use the get subcommand to determine the values for these two attributes. For example:
To display the value for the security-enabled attribute:
asadmin> get configs.config.server-config.admin-service.jmx-connector.system.security-enabled
To display the value for the type attribute:
asadmin> get configs.config.server-config.admin-service.type
If necessary, use the set subcommand to set security-enabled=false. For example:
asadmin> set configs.config.server-config.admin-service.jmx-connector.system.security-enabled=false
On Windows, when you upgrade cluster profile domains, you could encounter the following error:
Fatal error while backing up the domain directory
To resolve this error, look for and remove any hidden files in the source domain's directory and re-run Upgrade Tool.
This problem only occurs when using GlassFish Server 3.1 Upgrade Tool to perform a side-by-side upgrade on a 2.x domain without an Internet connection. It does not occur when using GlassFish Server 3.1.1.
The workaround for this issue is as follows:
Copy the older source domain to be upgraded to the new target as-install/domains directory.
Rename the target domain1 directory, if one exists, before proceeding.
Run the upgrade.
asadmin> start-domain --upgrade domain-name