Connections on DB2 for iSeries remain open even after WebSphere Application Server has closed them
 Technote (troubleshooting)
 
Problem(Abstract)
When connecting to a DB2® database on an iSeries™/AS400® host, connections appear to remain open even after WebSphere® Application Server has closed them. This is due to the way the iSeries Toolbox for Java™ set of Java Database Connectivity (JDBC™) drivers manage connections.
 
Resolving the problem
DB2 for iSeries/AS400 supports database connectivity through the toolbox for the Java set of JDBC drivers. The toolbox obtains its connections from a set of pre-start jobs, called QZDASOINIT jobs, on the database host server to hand out to WebSphere Application Server for its pool of connections.

Closing or discarding a connection from the pool does not correlate to closing a connection in the toolbox pool. These QZDASOINIT pre-start jobs on the database host are not stopped until the maximum number of uses is reached (the default is 200). Therefore, the connections tend to persist for a very long time.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Data & Information Management DB2 UDB for iSeries
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > DB Connections/Connection Pooling
Operating system(s): Windows
Software version: 6.0
Software edition:
Reference #: 1155292
IBM Group: Software Group
Modified date: Oct 28, 2004