Bug #11615 | Synchronization problem in realClose | ||
---|---|---|---|
Submitted: | 28 Jun 2005 17:29 | Modified: | 2 Aug 2005 18:14 |
Reporter: | Tony Walker | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 3.1.10 | OS: | Windows (Windows XP) |
Assigned to: | Mark Matthews | CPU Architecture: | Any |
[28 Jun 2005 17:29]
Tony Walker
[13 Jul 2005 14:24]
James Sangroniz
Saw a very similar failure, but on a different line. Here's the top of the stack trace java.lang.NullPointerException at com.mysql.jdbc.ServerPreparedStatement.realClose(ServerPreparedStatement.java:1089) at com.mysql.jdbc.Connection.closeAllOpenStatements(Connection.java:2879) at com.mysql.jdbc.Connection.realClose(Connection.java:2086) at com.mysql.jdbc.Connection.close(Connection.java:1060) Happens very infrequently, but is bothersom.
[13 Jul 2005 14:56]
Mark Matthews
A fix for this has been checked in, and is in the nightly snapshot builds at http://downloads.mysql.com/snapshots.php#connector-j I'd appreciate it if you could let me know if a binary from the snapshot build shows the same behavior (it shouldn't). Thanks, -Mark
[7 Aug 2005 13:18]
Tony Walker
Sorry for the delay in replying -- I've just got back to testing with MySQL. The bug appears to be gone. I haven't been able to reproduce it in several tests -- many more than it took previously. Thanks, Tony