APAR status
Closed as program error.
Error description
When an application such as a servlet spawns a new thread and
then creates a connection, the connection handle is normally
closed in this child thread. If however the handle is closed in
the parent thread that WebSphere controls, a memory leak can
occur.
The problem was discovered on a version 5.1.0 system.
Local fix
Close the connection handles in the thread that created them.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of JCA. *
****************************************************************
* PROBLEM DESCRIPTION: Possible memory leak when closing *
* connections on different threads. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A memory leak can occur if a getConnection occurs on a user
thread and the same connection is closed on an Application
Server thread.
In most cases, customer code will close the connection on the
same thread. This is only a problem for customer code that
uses the same connection on different threads. Using the same
connection on different threads is not recommended and could
result in other multi threaded issues.
Problem conclusion
With this fix a getConnection can occur on a user thread and
the same connection can be closed on an Application Server
thread without a memory leak.
The fix for this APAR is currently targeted for inclusion
in cumulative fixes 5.02.16, 5.1.1.10 and fixpack 6.0.2.9.
Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PK17508 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2006-01-06 |
Closed date |
2006-02-15 |
Last modified date |
2006-02-15 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS BASE 5.0 |
Fixed component ID |
5630A3600 |
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 |
|