[DBCP-350] Problem with DBCP 1.3 /jdk 6 and oracle spatial

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 1.3, 1.4
• Fix Version/s: 1.3.1, 1.4.1

Environment

CentOS 5.5 x86_64, Oracle JDK 1.6u22 32bit, Tomcat 5.5.31, ojdbc6.jar

• Assignee: Unassigned
• Reporter: Nils Hildebrand
• Created: 06/Dec/10 14:47
• Updated: 31/May/14 04:11
• Resolved: 11/Aug/11 09:58

Description

We have a GIS-application running on Tomcat 5.5. As webserver we are using
Apache httpd 2.2 connected to tomcat via ajp (mod_proxy_ajp).

The application worked fine with Tomcat 5.5.28 until we tried to upgrade to Tomcat 5.5.31.

After the upgrade we get - in certain situations a:
java.io.IOException: org.hibernatespatial.helper.FinderException: Couldn't get
at the OracleSpatial Connection object from the PreparedStatement.

After looking through the Tomcat 5.5 changelogs we stumbled across a change
made in 5.5.30: Upgrade to DBCP 1.3.

I can affirm now that the problem is gone when downgrading to DBCP 1.2.2.
The same problem occurs when using DBCP 1.4.

It seems something has changed from 1.2.2 to 1.3 that has partially broken Oracle-Locator operations in dbcp 1.3
I've seen some bug-reports for dbcp 1.3.1 which point in the same direction (oracle-db-error lead to java error) - perhaps these are the same problems...