Kbase P64254: JDBC connections are not reused nor trimmed when using WebSphere JDBC pooling.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/09/2010 |
|
Status: Verified
SYMPTOM(s):
Progress JDBC Manager
WebSphere Platform: 5.0 [BASE 5.0.2 ptf2M0325.01]
JDBC connections do not terminate properly.
JDBC clients are not reused within the connection pool.
Connection pool does not trim unused connections.
Shutdown of Websphere does not disconnect _sqlsrv2 processes.
EJB stateless session beans pass connection to business objects.
Business object is custom code to handle the database connection.
Websphere Connection Pooling Set-up Details
Sample connection pooling configuration in WebSphere v5 (SOME database):
Minimum Pool Size: 10
Maximum Pool Size: 15
Connection Timeout: 15 seconds (Number of seconds after which a connection
request is determined to have timed out)
Idle Timeout: 15 seconds
Orphan Timeout: 15 seconds
Statement Cache Size: 100
Auto Connection Cleanup: disabled. We explicitly close all connections.
FACT(s) (Environment):
Progress 9.1D
CAUSE:
Bug #20040129-023
CAUSE:
Bug# OE00100319
CAUSE:
The exact cause is unknown at the time of this writing
FIX:
Upgrade to 9.1D09 or later