Project

General

Profile

Bug #1709

"can't operate on a closed statement error" in log

Added by Constantin Asofiei over 11 years ago. Updated over 11 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version:

History

#1 Updated by Constantin Asofiei over 11 years ago

For this one, I didn't got a chance to do any more investigations. One of the issues was in ScrollingResults.cleanup. What might cause this would be a race condition, where two threads call ScrollingResults.sessionClosing at the same time - but I'm not sure this can happen; I mention this because, once the ScrollingResults.closed flag is set to TRUE, it no longer be set back to FALSE; only explication would be a race condition, so synchronizing the ScrollingResults.cleanup method on its object instance may be a solution. Beside this, I don't have any other relevant info.

Original requirements:

Please look into the old "Can't operate on a closed statement" warning Hibernate logs sometimes when closing the delegate ScrollingResults object used by a ProgressiveResults object (converted FOR EACH loops). I don't have a particular recreate for this, but it is the same issue you looked at (and partially fixed) once before. Please go back through e-mail to see if you can dig up a recreate. Your previous fix for this seems to have prevented some cases of this, but we still have seen the warning logged on many occasions in proxeee logs.

Also available in: Atom PDF