APAR status
Closed as program error.
Error description
In version 5 of WebSphere, a parked connection handle is formed
for sharable connections. Some applications may count createMana
gedConnection() and get an improper count of actual connections
in use. This can be avoided by using Smart Connection Handles in
a resource adapter. However, this parked connection handle is
not really necessary for Unshareable Connections. This fix
backports version 6 behavior for this and will not create the
parked connection handle for an unshared connection.
Local fix
Use Smart Connection Handles:
http://www-128.ibm.com/developerwo
rks/websphere/library/techarticles/0302_kelle/kelle.html
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of *
* resource adapters that do not support *
* inactive connection support (smart handles). *
****************************************************************
* PROBLEM DESCRIPTION: Customers using a resource adapter *
* that does not support inactive *
* connection support, will have a *
* parked connection created when using *
* shared or unshared connections. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
With this update, the creation of the parked connection is
delayed until a shared connection is used. So, if only
unshared connections are used, the parked connection will not
be created. This applies to all resource adapters. If
shared connections must be used, then the resource adapter
must implement inactive connection support, if the parked
connection is an issue.
Problem conclusion
Inactive connection support is the preferred way to remove
the need for a parked connection. Resource adapter providers
should implement inactive connection support.
Since some of the resource adapter providers are choosing
not to implement inactive connection support, this additional
update will help users using unshared connections.
The fix for this APAR is currently targeted for inclusion
in fixpack 5.02.10 an 5.1.1.4.
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 |
PK00210 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10H |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-01-28 |
Closed date |
2005-03-09 |
Last modified date |
2005-03-09 |
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 |
|