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.

HTTP Service Statistics attributes discrepancies (7018903)

Description

There are typographical errors in the names of two HTTP Service statistics listed in HTTP Service Statistics in Sun GlassFish Enterprise Server v2.1.1 Administration Guide.

Solution

Please note the following corrections in the list of HTTP Service statistic names:

• processing-time should be processingtime

• request-count should be requestcount

Glassfish GFv2 Mod_JK AJP listens to all interfaces (7008190)

Description

The instructions provided in Using mod_jk in Sun GlassFish Enterprise Server v2.1.1 Developer’s Guide for configuring an Apache JServ Protocol (AJP) listener with mod_jk are incorrect with regard to port, address, and other connector configuration options. The instructions as written will configure the AJP listener to listen on all interfaces rather than on any specific interface that you may try to define in the worker.properties file.

Solution

The documentation implies that, in addition to setting the required options in the httpd.conf file, AJP listener configuration settings can be defined in either the worker.properties file or the glassfish-jk.properties file. However, it is necessary to define configuration settings in both worker.properties and glassfish-jk.properties, rather than in just one or the other.

The following examples augment the instructions in Using mod_jk in Sun GlassFish Enterprise Server v2.1.1 Developer’s Guide.

The first example shows a workers.properties file that is configured for mod_jk.

# Define 1 real worker using ajp13
worker.list=worker1
# Set properties for worker1 (ajp13)
worker.worker1.type=ajp13
worker.worker1.host=localhost worker.worker1.port=8009

The next example shows the corresponding Enterprise Server configuration settings that are defined in the glassfish-jk.properties file.

# Set the glassfish-jk.properties (for port)
# See http://tomcat.apache.org/tomcat-5.5-doc/config/ajp.html for other options
port=8009

The glassfish-jk.properties is also where you should specify any other options for the connector on the Enterprise Server side.

[UB]The *Global Transaction support box* is nowhere to be found (7536)

Description

The following statement appears in Transaction Scope in Sun GlassFish Enterprise Server v2.1.1 Developer’s Guide:

In the Enterprise Server, a JDBC resource is non-XA if it meets any of the following criteria:

• In the JDBC connection pool configuration, the DataSource class does not implement the javax.sql.XADataSource interface.

• The Global Transaction Support box is not checked, or the Resource Type setting does not exist or is not set to javax.sql.XADataSource.

There are several errors in this statement:

• The word “any” in the first sentence should be “either.”

• “DataSource” is a class name but the text formatting does not reflect this.

• A “Global Transaction Support” checkbox does not exist anywhere in the Enterprise Server 2.1 or v2.1.1 Admin Console.

Solution

The correct statement should read:

In the Enterprise Server, a JDBC resource is non-XA if it meets either of the following criteria:

• In the JDBC connection pool configuration, the DataSource class does not implement the javax.sql.XADataSource interface.

• The Resource Type setting is not set to javax.sql.XADataSource.

Misleading Documentation for Configuring JMS Physical Destinations

Description

The following statement appears in JMS Physical Destinations in Sun GlassFish Enterprise Server v2.1.1 Administration Guide:

To create a physical destination from the Admin Console, select Configuration > Java Message Service > Physical Destinations.

Solution

The statement should read:

To create a physical destination from the Admin Console:

1. Navigate to the Physical Destinations page.

   • For a cluster in a domain that supports clusters and stand-alone instances, select Clusters > cluster-name > Physical Destinations.

     cluster-name is the name of cluster for which you are creating a physical destination.

     Domains that are created with the cluster profile or enterprise profile support clusters and stand-alone instances.

   • For an instance or the DAS in a domain that supports clusters and stand-alone instances, select Stand-Alone Instances >instance-name > Physical Destinations.

     instance-name is the name of instance for which you are creating a physical destination. For the DAS, instance-name is server (Admin Server).

   • In a domain that does not support clusters and stand-alone instances, select Configuration > Java Message Service > Physical Destinations.

     Domains that are created with the developer profile do not support clusters and stand-alone instances.

2. On the Physical Destinations page, click New.

   The New Physical Destination page opens.

Furthermore, references to “Create Physical Destinations page” should read “New Physical Destination page.”

Upgrade Procedure is Confusing

Description

The following information in Upgrading the Runtime Binaries of a Package-Based Installation of Application Server in Sun GlassFish Enterprise Server v2.1.1 Upgrade Guide is no longer correct:

• The statement in the introduction that patches are available from the SunSolve program site

• The list of links in Step 2 of the procedure

Solution

Ignore the statement in the introduction and the links in Step 2 of the procedure. Instead, search the My Oracle Support site for patches to download. In your search, specify the following filters:

• Product: Sun GlassFish Enterprise Server

• Release: Sun GlassFish Enterprise Server v2.1.1