Documentation

Various IDs 

Javadoc Inconsistencies. 

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.

6219689 

Error in ConnectionPoolStats API documentation.

The API documentation in install_dir/docs/api states:

public CountStatistic getNumConnFree()

This entry should read: 

public RangeStatistic getNumConnFree()

6265624 

Bundled ANT throws java.lang.NoClassDefFoundError.

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

Solution

Using the bundled ANT for activities outside the Application Server is not recommended. 

6482223 

Differences in default values in creating new JMS connection factory for online help and documentation. 

When creating a new JMS connection factory, the online help and the Administration Guide differ in the list of default values for the connection factory. Specifically, the online help lists the following:

======================================= 
ReconnectAttempts      : 6 
UserName               : guest 
ReconnectInterval      : 30000 
ReconnectEnabled       : false 
Password               : guest 
ClientId               :  
AddressListBehavior    : PRIORITY 
AddressListIterations  : -1 
AddressList            : 7676 
=======================================

The Administration Guide lists the following:

======================================= 
ReconnectAttempts      : 3 
UserName               : guest 
ReconnectInterval      : 30000 
ReconnectEnabled       : true 
Password               : guest 
ClientId               :  
AddressListBehavior    : RANDOM 
AddressListIterations  : 3 
AddressList            : 7676 
=======================================

Solution

The information in the Administration Guide is correct.

6486123 

Documentation on getting a physical Connection from a wrapped Connection is no longer correct. 

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.1 2005Q2 Developer’s Guidesection of Chapter 11, Using the JDBC API for Database Access, in Sun Java System Application Server Enterprise Edition 8.1 2005Q2 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);

6511489 

Additional information needed to explain KeepAliveFlushes and KeepAliveRefusals.

The Application Server Tuning Guide should contain the following additional information about KeepAliveFlushes and KeepAliveRefusals.

In the current version of Application Server, the server does not close existing connections when the KeepAliveCount exceeds the MaxKeepAliveConnections. Instead, new keep-alive connections are refused and the KeepAliveResusals count is incremented.