Bug #9562 | Operation not allowed after ResultSet closed | ||
---|---|---|---|
Submitted: | 1 Apr 2005 16:10 | Modified: | 31 Mar 2014 9:09 |
Reporter: | Michael Small | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | nightly-20050331 | OS: | Windows (Windows 2000) |
Assigned to: | Alexander Soklakov | CPU Architecture: | Any |
[1 Apr 2005 16:10]
Michael Small
[1 Apr 2005 16:14]
Michael Small
I forgot to mention (because I removed other finder methods) that the line numbers listed do not correlate with the code I put in the bug listing. For clarification, I have received the problems at the following code lines in the loadTascClient(): vo.setTaxId(...) vo.setZipcode(....) vo.setStatus(...)
[1 Apr 2005 16:17]
Michael Small
Another note, the ResultSet returned is large (roughly 130,000 records). Could it possibly be that size of the ResultSet is causing the problem?
[1 Apr 2005 16:20]
Mark Matthews
The only way this could happen is if _something_ is closing the result set. Are you sure you're not experiencing the connection dying somewhere along the way (check your server's error log), because the JDBC specification requires that 1) A communications error closes the connection, and 2) That closing a connection implicitly closes all open statements, and that 3) closing a statement implicitly closes all open result sets. Could you tell us what happens if you run your application with the following configuration parameter added to your JDBC URL? 'holdResultsOpenOverStatementClose=true'
[1 Apr 2005 16:36]
Michael Small
It appears to running correctly now. I ready the documentation on this property (as well as your comment about something closing the Connection/Statement/Result), but this code is running in a single threaded application. No other objects are using the same DAO object. The statements (and connection) are closed in the finalize() method of the object (as inherited by it's parent com.tasc.dao.mysql.MySqlDao class).
[1 Apr 2005 16:49]
Michael Small
Is there a way I can turn on debugging of the ResultSet? Is it possible that a error is occurring between the driver and the server that is closing the Connection/Statement/ResultSet without throwing an error (which then manifests later when I call a getter method of the ResultSet)?
[1 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:09]
Alexander Soklakov
I close this report as "Not a Bug". Please, feel free to reopen it if the problem still exists in current driver.