PQ67535, 4.0.5: StaleconnectionException thrown on
JNDI lookup
Downloadable files
Abstract
StaleConnectionException is thrown when there are stale
JDBC™ connections and a client attempts a JNDI™ lookup.
Download Description
PQ67535 resolves the following problem:
USERS AFFECTED:
Users of WebSphere® Application Server Advanced Edition V4.0.5 or any V4.0
releases prior to V4.0.5.
PROBLEM DESCRIPTION:
When the administrative repository database server is stopped and
restarted, name server operations against the database will initially
fail, when in principle, the name server could retry the naming operation.
This would avoid the need for naming clients to perform the retry.
When stale JDBC connections are in the WebSphere Application Server
connection pool, the name server will receive a StaleConnectionException
when it uses a stale connection to access the name space database. Since
the connection pool is flushed of all stale connections when the
StaleConnection exception is thrown, and since Naming operations are
performed with a new transaction (so that a rolled back transaction does
not create a problem), the naming operation can be retried (with a new
transaction). Before this fix, the name server attempted no retries and
instead, threw an exception. This exception will usually be externalized
as a JNDI NamingException because naming clients are typically JNDI
clients.
PROBLEM CONCLUSION:
Retry logic was added to the name server so that operations resulting in
unexpected exceptions are retried. New properties were defined to control
the number of retries (com.ibm.websphere.naming.db.retrycount, with a
default of 2) and the delay between retries
(com.ibm.websphere.naming.db.retrydelay with a default of 2000
milliseconds).
Prerequisites
None
Installation instructions
Please review the readme.txt for detailed installation
instructions.