https://issues.apache.org/bugzilla/show_bug.cgi?id=50326
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #1 from Mark Thomas <ma...@apache.org> 2010-11-24 07:24:10 EST ---
(In reply to comment #0)
> DBCP 1.4 binaries should be used by applications running under JDK 1.6.
> DBCP 1.3 should be used when running under JDK 1.4 or 1.5."
>
> Now Tomcat should run with jdk 1.5 and jdk 1.6 (and worked fine with the dbcp
> 1.2.x as it seems). This seems to be a bug here.
This analysis is incorrect since the JDK limitations of DBCP 1.2 are identical
to DBCP 1.3 (it is related to the JDBC version supported by the JRE).
> Since jdk 1.5 has reached EoL I think a proper solution would be to update
> dbcp
> to 1.4 in Tomcat 5.5
That is not possible since DBCP 1.4 requires Java 6 but the minimum Java
version for Tomcat 5.5.x is Java 1.4 and that will not be changed.
> - or fix dbcp 1.3 so it is compatible with jdk 1.6.
That is simply not possible. Hence why there is DBCP 1.3 and DBCP 1.4.
> Else the statement that 5.5 runs with jdk 1.5 or higher is no longer true.
The statement that 5.5 runs on a 1.4 or higher jre is perfectly true. There is
nothing stopping DBCP 1.2 or 1.3 running on Java 6. However, JDBC 4 features
will not be available and any attempt to use them will result in an exception.
> I could not test our current application with Tomcat 5.5.31 and jdk 1.5 since
> it is compiled now against jdk 1.6 and won't work with jdk 1.5 any longer.
That shouldn't stop you testing it with 5.5.31 running on a 1.6 jre.
I suspect you have hit either a DBCP bug or a hibernate bug around the
relationship between physical and pooled connections and what is exposed via
prepared statement objects. The Commons users list is probably the best place
to get help debugging this. It certainly isn't a Tomcat bug.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
