Bug #10127 | Operation now allowed on closed ResultSet | ||
---|---|---|---|
Submitted: | 24 Apr 2005 14:47 | Modified: | 31 Mar 2014 9:19 |
Reporter: | Srinivas Somayajula | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | OS: | Any | |
Assigned to: | Alexander Soklakov | CPU Architecture: | Any |
[24 Apr 2005 14:47]
Srinivas Somayajula
[27 Apr 2005 17:18]
Mark Matthews
Something is closing the connection out from underneath you, which in turn closes the statement, which in turn closes the result set (as is required by the JDBC spec). Are you using a connection pool? Sharing connections? Is there anything in your MySQL server's error log about killing a connection?
[27 May 2005 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[31 Mar 2014 9:19]
Alexander Soklakov
I close this report as "Can't repeat" because there is no feedback for a long time and codebase is too old. Please, feel free to reopen it if the problem still exists in current driver.