APAR status
Closed as program error.
Error description
Error Symptom:
Settings
jdbc provider: DB2 Universal JDBC Driver Provider (XA)
data source:
name: XA
JNDI: jdbc/sample
Connection Pool:
Connection Timeout: 150
Max. Connections: 10
Min. Connections: 5
Reap time : 60
Unused timeout: 150
Aged timeout: 0
Purge Policy: EntirePool
.
When an error is encountered that should cause the pool to be
purged, like a StaleConnectionException, the pool manager leaves
the Min. Connections number of connections open.
It requires subsequent errors being generated on each
remaining connection to get all of these closed so that a new
connection can be opened.
.
The timing window where the stale connection occurs after the
conncetion has been created, but
before it's enlisted causes problems passing the correct
information to the various WebSphere components.
This APAR also will make sure that the correct information is
passed along and that we process that information correctly
will take some time and may require coordination between J2C,
the RRA and JTS.
(What external symptom does this cause? )
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of *
* JDBC, JMS, or JCA transactional Connections. *
****************************************************************
* PROBLEM DESCRIPTION: If a StaleConnection exception is *
* caused by a transaction exception the *
* original connection will be removed *
* from the pool as usual. However any *
* other connections in the pool will *
* not be removed, resulting in further *
* StaleConnectionExceptions until the *
* pool is empty. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If a StaleConnectionException occurs as the result of a
transaction exception, the connection pool will not be purged
regardless of the purge policy. Any connections in the pool
will not be removed until they receive
StaleConnectionExceptions.
Problem conclusion
Created a separate transactionError flag which causes the
failing connection to be removed, and allows any future
ConnectionErrorEvents on that connection to be handled as
usual (the pool will be purged according to the purge policy).
Temporary fix Comments
APAR information |
APAR number |
PQ87572 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-04-15 |
Closed date |
2004-05-13 |
Last modified date |
2004-05-13 |
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 |
|