Documentation

This section describes known documentation issues and associated solutions.

Javadoc Inconsistencies (various IDs)

The Javadoc for several AMX interfaces and methods is either missing or incorrect:

• Getter methods for NumConnAcquired and NumConnReleased statistics are missing from ConnectorConnectionPoolStats and AltJDBCConnectionPoolStats. These getter methods will be added in a future release as getNumConnAcquired() and getNumConnReleased().

• Calling the following methods in EJBCacheStats will throw an exception: getPassivationSuccesses(), getExpiredSessionsRemoved(), getPassivationErrors(), getPassivations(). This will be fixed in a future release.

• The AMX MBeans may require several seconds after server startup before they are all registered and available for use. A future release will make it possible to determine when the AMX MBeans are fully loaded.

• The constant XTypes.CONNNECTOR_CONNECTION_POOL_MONITOR is misspelled ("NNN"). This will be corrected in a future release.

GlassFish 2.x documentation referring to invalid create-session-store command (6935976)

Description

Several locations in the GlassFish 2.x documentation set refer to the deprecated create-session-store subcommand.

Solution

Use the create-ha-store subcommand instead of the deprecated create-session-store subcommand. For example, change the following command:

asadmin create-session-store --storeurl url --storeuser user --storepassword password --dbsystempassword password

to

asadmin create-ha-store --user user --passwordfile filename databasename

GlassFish 2.1.1: behavior with applications containing identical context roots is undocumented (7002836)

Description

The Domain Administration Server (DAS) in versions of Sun GlassFish Enterprise Server prior to v2.1.1 did not allow multiple applications to be deployed using the same web context root, even if those applications were targeted for different Enterprise Server instances.

This behavior was changed in Enterprise Server v2.1.1, and the DAS now supports the deployment of applications using the same context root as long as those applications are deployed to different Enterprise Server instances. However, this new DAS support is not sufficiently documented.

Solution

Deploying a WAR Module in Sun GlassFish Enterprise Server v2.1.1 Application Deployment Guide states:

Web module context roots must be unique within a server instance.

While technically accurate, it is useful to add the following further clarification to this statement:

The DAS in Sun GlassFish Enterprise Server versions v2.1.1 and later supports the deployment of multiple web applications using the same web context root as long as those applications are deployed to different Enterprise Server instances. Deploying multiple applications using the same context root within a single Enterprise Server instance will produce a DAS error.