You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2002/09/21 02:04:07 UTC
DO NOT REPLY [Bug 12888] New: -
[jelly] JDBC sql result set leak
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=12888>.
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=12888
[jelly] JDBC sql result set leak
Summary: [jelly] JDBC sql result set leak
Product: Commons
Version: unspecified
Platform: All
OS/Version: Windows NT/2K
Status: NEW
Severity: Critical
Priority: Other
Component: Sandbox
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: hr_stoyanov@yahoo.com
Hi-,
There is JDBC result set leak in the <sql:query ...> tag.
At the end of doTag() for the org.apache.commons.jelly.tags.sql.QueryTag,
a ResultImpl object ("result") is constructed and it is handed over the result
set ("rs").
However, neither ResultImpl nor QueryTag objects close the rs object at the end,
which leads to "cursor leak" (In Oracle: ORA-01000: maximum open cursors
exceeded)
Hint: try to close the result set in the finally{} block at the end of
QueryTag.doTag()
Thanks,
Hristo
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>