Description: Jobs with JDBC activities will be stalled once the number of completed jobs reaches the Max Connections set on the JDBC connection resource. For example, if you have a process (see the attached screenshot, filename: starting.png) with JDBC Connection resources set with 10 Max Connections, a Timer set to run at some interval of time and JDBC Query activity, you can see that all the new jobs created after the number of completed jobs reach 10 are stalled on running it in the debugger, even when 10 jobs are completed.
Symptoms: The Jobs will be stalled in debugger showing up as Starting as seen in attached screenshot (
Filename: starting.png). Cause: Oracle JDBC Driver version is 11.1.x.y. You can confirm the version by extracting up the ojdbc6.jar and looking up the Implementation version in the manifest file (Manifest.mf).
+++
Manifest-Version: 1.0
Implementation-Vendor: Oracle Corporation
Implementation-Title: ojdbc6.jar
Implementation-Version: Oracle JDBC Driver version - "11.1.0.6.0-Production+"
Implementation-Time: Tue Oct 30 03:33:58 2007
Specification-Vendor: Oracle Corporation
Sealed: true
Created-By: 1.6.0 (Sun Microsystems Inc.)
Specification-Title: Oracle JDBC driver classes for use with JDK6
Specification-Version: Oracle JDBC Driver version - "11.1.0.6.0-Produc
tion+"
Main-Class: oracle.jdbc.OracleDriver
Name: oracle/sql/converter_xcharset/
Sealed: false
Name: oracle/sql/
Sealed: false
Name: oracle/sql/converter/
Sealed: false
+++++++++++
It is possible that the driver is not releasing connections back to the pool for the completed jobs.