Ping Connection Pool
By shalini_m on Dec 23, 2009
While a JDBC/Connector Connection pool is created, there was no way of identifying the erroneous values for some of the attributes. With the introduction of a new attribute "ping" in GlassFish V3, its possible to do so.
An incorrect value of a database connectivity property is another case where pooling infrastructure does not warn the user when pool is created or reconfigured.
For example, if a user tries to set a wrong value for isolation level during creation like :
asadmin create–jdbc–connection–pool ........ ––isolationlevel xyz poolName
The erroneous isolation level is identified only at runtime when the pool is initialized. A get connection from an application following this would throw a WARNING message. This can be identified at an earlier stage by setting a flag like
asadmin create–jdbc–connection–pool ........ ––isolationlevel xyz --ping=true poolName
The default value of this flag is false.
The Ping button in admin console as well as the admin CLI command asadmin ping-connection-pool are still supported in GlassFish V3.
 Ping CLI Command