You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2003/08/01 14:13:41 UTC
DO NOT REPLY [Bug 22050] New: -
esql and max open cursors
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22050>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22050
esql and max open cursors
Summary: esql and max open cursors
Product: Cocoon 2
Version: Current CVS 2.1
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: core
AssignedTo: dev@cocoon.apache.org
ReportedBy: gguillemot@rennes.jouve.fr
I'm using the esql with an Oracle database and when I have too many SQL errors
during the connection, Oracle returns an ORA-1000 Maximum open cursors exceeded.
After a search on the web, I found the problem occurs when resultSet and
Statement are not closed.
It seems that in the esql.xsl file, in the "esql:connection//esql:execute-query"
template, when a SQLException exception is catch, the resultSet and the
statement are effectively not closed.
After addin a finally condition to close the resultSet and the Statement, the
error did not occur anymore.