PQ48135: WEBSPHERE OBTAINING 130 CONNECTIONS TO DB2 WITH MAX CONNECTIONS SET TO 10.


APAR

APAR status
Closed as program error.

Error description
When connection pool max is set to 10, when running over 20 conc
current clients against the server, 130 connections were made to
DB2.
Defect 99623 already exists for this problem.
Local fix
Problem summary
Connection pool min was set at 0.  The max was set at 10.
When running about 20 concurrent clients against the server,
up to 130 connections were being obtained at DB2.
.
Upon investigation, it was determined that in the
ConnectionPool.java method waitForVictimConnection, there
was a synchronization block that wasn't large enough.
Problem conclusion
By moving the location of the synchronization to synchronize
around the larger area, local tests proved that only 10
connections were being obtained from DB2.
Code was changed in: com/ibm/ejs/cm/pool/ConnectionPool.java
Temporary fix
Comments
APAR information
APAR numberPQ48135
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-04-24
Closed date2001-05-23
Last modified date2001-05-23

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
JDBC
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED SU
Fixed component ID5648C8402

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ48135
IBM Group: Software Group
Modified date: 2001-05-23