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.

Bundled ANT throws java.lang.NoClassDefFoundError (6265624)

Description

The following exception is thrown in thread "main" java.lang.NoClassDefFoundError: org/apache/tools/ant/launch/Launcher.

Solution

Use the bundled ANT for things outside the Application Server is not recommended.

Online help does not describe how to create a JMS physical destination for a specific server instance or cluster. (6808339)

Use the following procedure to create configuration-specific JMS physical destinations:

1. Log on to the Admin Console.

2. In the left-hand pane, click Standalone Instances > instance_name. If you are using clusters, click Clusters > cluster_name.

3. Click the JMS Physical Destinations tab.

4. Click New.

5. Create a Queue and Topic.