This section describes known documentation issues and associated solutions.
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.
Use the following procedure to create configuration-specific JMS physical destinations:
Log on to the Admin Console.
In the left-hand pane, click Standalone Instances > instance_name. If you are using clusters, click Clusters > cluster_name.
Click the JMS Physical Destinations tab.
Create a Queue and Topic.
The example in the man page is missing the operand at the end of the command. An error occurs if the command is entered as shown in the example. Correct example is:
asadmin> ping-connection-pool --user admin1 --passwordfile pwordfile sampleConnectionPool