Closing Resultset goes in error db driver

panglaoying / log4jdbc-log4j2

Automatically exported from code.google.com/p/log4jdbc-log4j2

0 stars 0 forks source link

Closing Resultset goes in error db driver #5

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. create Entity Manager

What is the expected output? What do you see instead?
N/A

What version of the product are you using? On what operating system?
H2 1.3.172
1.14 JDBC 4
tomcat dbcp 1.3
EclipseLink 3.4.1

Please provide any additional information below.
In our Apache Tomcat Virgo Server (most probably J2EE also), setup of 
persistence fails.
Without proxy db driver work perfect, also the original log4jdbc (ver 1.2) 
works good.

Original issue reported on code.google.com by nikolas....@gmail.com on 20 Jun 2013 at 1:39

Attachments:

error.log

GoogleCodeExporter commented 9 years ago

Original comment by frederic...@gmail.com on 20 Jun 2013 at 7:31

Changed state: Started

GoogleCodeExporter commented 9 years ago

Thank you for reporting the issue. I pushed a fix on the svn and on Maven, see 
revision r171 and release 1.15-SNAPSHOT. Could you please tell me if this fixes 
your problem? (because I suspect it might also be a configuration issue)

I think the problem was that the driver you use does not support the use of a 
ResultSetMetaData when the related ResultSet is closed, even if the 
ResultSetMetaData was obtained before closing; this behavior does not seem to 
be a JDBC specification. 
Now, the information needed is stored immediately when the ResultSetMetaData is 
obtained; The ResultSetMetaData is no longer stored for later use.

As of log4jdbc, it is normal that no error appears, because it doesn't 
implement the ResultSetCollector feature of log4jdbc-remix :)

Original comment by frederic...@gmail.com on 20 Jun 2013 at 8:05

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

I have pushed the release to the main branch (release 1.15), please let me know 
if your problem is fixed.

Original comment by frederic...@gmail.com on 20 Jun 2013 at 11:39

GoogleCodeExporter commented 9 years ago

With version 1.15 server is started and running, our db test suites pass with 
success.

The issus for is fix, thank you.

Original comment by nikolas....@gmail.com on 21 Jun 2013 at 9:47

GoogleCodeExporter commented 9 years ago

* The issue for me is fix, thank you.

Original comment by nikolas....@gmail.com on 21 Jun 2013 at 9:48

GoogleCodeExporter commented 9 years ago

Thanks for letting me know :)

Original comment by frederic...@gmail.com on 21 Jun 2013 at 11:21

Changed state: Verified