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.
The following exception is thrown in thread main: java.lang.NoClassDefFoundError: org/apache/tools/ant/launch/Launcher.
Use the bundled ANT for things outside the Application Server is not recommended.
The Sun Java System Application Server Enterprise Edition 8.2 Performance Tuning Guide incorrectly states the following about Log Options:
The Administration GUI provides the following two logging options:
Option 1 – Log stdout (System.out.print) content to the event log
Option 2 – Log stderr (System.err.print) content to the event log
These log options no longer exist in Application Server Enterprise Edition 8.2.
The Application Server Enterprise Edition 8.2 documentation discusses an HTTP file caching feature, in HTTP File Cache in Sun Java System Application Server Enterprise Edition 8.2 Performance Tuning Guide. However, this feature was not included in Application Server Enterprise Edition 8.2. Note that this feature has been reintroduced in Application Server 9.0.
As a result of other defects (possibly 6295215) the code provided in the Obtaining a Physical Connection from a Wrapped Connection in Sun Java System Application Server Enterprise Edition 8.2 Developer’s Guide section of Chapter 11, Using the JDBC API for Database Access, in Sun Java System Application Server Enterprise Edition 8.2 Developer’s Guide is not correct. Specifically, the line:
Connection drivercon = ds.getConnection(con);
should now read:
Connection drivercon = ((com.sun.gjc.spi.DataSource)ds).getConnection(con);