APAR status
Closed as program error.
Error description
Customer has configured their datasource connection to be an
unshareable managed connection. If a command like,
"db2 force applications all" is done (which simulates a db
server restart), then the connections that were in-use at the
time that the command is done are "lost".
This problem only happens when non-sharable connections are
used. If shareable connections are used, the problem does not
occur.
The symptoms that are seen in the WebSphere logs are
a SQL30081N with retuen code of 10053 and a either a CLI0106E OR
a CLI0108E.
These result in a StaleConnectionException being thrown, and a
CONM7007I being logged in the stdout log. This will contain the
CLI error message as the cause and will show the associated
ErrorCode -99,999 amd SQLState 08003. It is possible that a
different ErrorCode and SQLState are logged.
.
Keywords: CONM7007I StaleConnectionException shareable CLI0106E
CLI0108E database server restart connection pool EntirePool
FailingConnectionsOnly
Local fix
Use shareable as opposed to non-shareable connections (if you
are able to)
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of *
* JDBC, JCA and JMS connections. *
****************************************************************
* PROBLEM DESCRIPTION: If an unsharable connection *
* encounters a stale connection it may *
* not be returned to the connection pool. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If an unsharable connection encounters a stale connection or
ConnectionError it may not be returned to the connection pool.
When the pool fills up the customer may see
ConnectionWaitTimeoutExceptions, or they may notice too many
connections open to the EIS (i.e DB2 or CICS).
Problem conclusion
Unsharable connections are released to the connection pool
regardless of whether there is an open handle when the
transaction completes. Since there is only one connection
handle to the connection at any given time, we know the handle
has received the connection error or stale connection signal.
Temporary fix Comments
APAR information |
APAR number |
PQ86120 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-03-16 |
Closed date |
2004-04-20 |
Last modified date |
2004-04-20 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|