Fixes are available
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
A temporary delay in getting connections can occur when maximum connections is too low and two or more connections are needed for the same thread. In addition to the delay, connection wait timeout exceptions will occur around the time of the connection wait timeout configured value. If the default values is used of 180 seconds, the delay will last approximately 180 seconds followed by connection wait timeouts.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server J2EE Connector Architecture ( JCA ) * * and IBM WebSphere Commerce * **************************************************************** * PROBLEM DESCRIPTION: Two connections per thread are needed * * for completing some transactions when * * using IBM WebSphere Commerce causing * * a delay. * **************************************************************** * RECOMMENDATION: * **************************************************************** A delay up to the connection wait timeout can occur at random times when using IBM WebSphere Application Server and IBM WebSphere Commerce.
Problem conclusion
Two custom properties have been provided to configure a pool reserve of connections to handle the second connection on the same thread. This prevents the temporary delay. To use this feature, create a new custom property on the connection pool, for the Datasource or Connection Factory. For Example: From the Administrative Console , navigate to the following path: JDBC providers > DB2 Universal JDBC Driver Provider > Data sources > DB2 Universal JDBC Driver DataSource > Connection pools > Custom Properties The property can be created by clicking the new button The following 2 properties available.: NOTE: All names and values are case sensitive. NAME Normal value Possible Values numberOfPoolReserves 1 1 -5 maxConnectionsInPoolReserve 1/3 the size of the main connection pool (This value is optional and will default to 1/3 the size of the main pool) In most cases, users who need this function will have been asked to increase the pool property max connection to a larger value to account for the 2 connections per thread. Example, You may have been using 10 max connections and you encounter the delay and are using IBM WebSphere Commerce. To avoid the delay its likely IBM WebSphere Commerce asked you to increase to 20 max connections. With this function, you will be able to return to 10 total connections by setting the number of pool reserves to 1 and max connection in the pool reserve to 1. The main pool max connection should be set to 9. Or you may be able to go back to 10 max connections for the primary connection pool and use number of pool reserves 1. This will automatically give you 3 connections in the pool reserve with a total of 13 connection being used. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.27, 8.0.0.5 and 8.5.0.1. 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
PM68323
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-07-06
Closed date
2012-08-23
Last modified date
2012-08-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
29 October 2021