This section describes restrictions and deprecated functionality in Oracle GlassFish Server 3.1 and 3.1.1.
The following topics are addressed here:
GlassFish Server 3.1–3.1.1 does not support node agents. When updating from installations of earlier product versions in which node agents were configured, the cluster definitions will be migrated, but the clustered instances themselves must be manually recreated. See Upgrading Clusters and Node Agent Configurations in Oracle GlassFish Server 3.1 Upgrade Guide for more information.
GlassFish Server 3.1–3.1.1 does not support HADB or the hadbm management command.
Instead of HADB, GlassFish Server 3.1-3.1.1 supports high availability clustering by means of in-memory session state replication and Active Cache for GlassFish. See Chapter 1, High Availability in GlassFish Server, in Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide for more information.
In GlassFish Server 3.1-3.1.1, it is recommended that utility options of the asadmin command precede the subcommand. Utility options are options that control the behavior of the asadmin utility, as distinguished from subcommand options. Use of the following options after the subcommand is deprecated.
Options in Table 1-4 are deprecated or no longer supported, or are obsolete and are ignored.
Table 1-4 Deprecated, Unsupported, and Obsolete Options for asadmin and Subcommands
The directory location of Java DB in GlassFish Server 3.1-3.1.1 has changed from its location in previous installations. Suppose that you have deployed applications that use Java DB databases in your previous server installation, and you upgrade your existing installation to GlassFish Server 3.1-3.1.1. If you run the asadmin start-database command and successfully start Java DB, you could run into problems while trying to run applications that were deployed on your previous server installation.
To solve this problem, you can copy the databases directory from your previous installation to as-install/databases. Make sure the database is not running when you do this.
Alternatively, you can perform these steps:
Use the asadmin start-database command with the --dbhome option pointing to the databases directory in the older version of Java DB. For example:
asadmin start-database --dbhome c:\glassfish\databases
After upgrade, start GlassFish Server 3.1-3.1.1.
By default, the GlassFish Server DAS uses the Client VM to achieve best startup and deployment performance. If you are using Windows AMD64, edit the domain.xml file to remove the line <jvm-options>–client<jvm-options>. In this case, JVM ergonomics chooses the appropriate kind of VM for the given platform. Note that server instances use the Server VM by default.
For more information about platform support, see Ergonomics in the 5.0 Java Virtual Machine.
The Metro Reliable Messaging in InOrder Delivery mode has not been tested for high availability in GlassFish Server 3.1-3.1.1. The feature may work, but it has not been formally tested and is therefore not a supported feature.
GlassFish Server 3.1.1 does not support Kerberos on the AIX platform.
For the complete report about this issue, see GLASSFISH-16728.
In Chapter 11, Extending and Updating GlassFish Server, in Oracle GlassFish Server 3.1 Administration Guide, the tools for updating software on a deployed server are listed as Update Tool, the pkg command, and the Administration Console. On AIX, only the pkg command is supported.
When you use the GlassFish Server installer in default mode on AIX, the Install Update Tool option is enabled, resulting in the following error:
Update Tool Bootstrap Not Configured
Use the following workaround:
Deselect the option to install Update Tool during installation.
Open the as-install/.org.opensolaris,pkg/cfg_cache file in a text editor.
Edit and save the file according to your edition of GlassFish Server:
For Oracle GlassFish Server, change this line in the file:
to this line:
For GlassFish Server Open Source Edition, change this line in the file:
to this line:
Run the pkg command from the as-install/bin directory to install the pkg client.
GlassFish Server and Coherence*Web serialize EJB references differently. Therefore, GlassFish Server 3.1.1 does not support persistence of EJB references in HTTP sessions when Coherence*Web is the persistence type.