[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1218) ResultSet not explicitly closed in JDBCPersistenceManager
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1218?page=comments#action_1... ]
Kevin Conner commented on JBMESSAGING-1218:
-------------------------------------------
It is certainly not benign to use up all cursors :)
I believe we are going to document this issue on the SOA platform and wait for your fix to
be incorporated into the EAP.
ResultSet not explicitly closed in JDBCPersistenceManager
---------------------------------------------------------
Key: JBMESSAGING-1218
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1218
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.4.0.SP3.CP01, 1.4.1.beta1
A ResultSet is left open at line 924 JDBCPersistenceManager:loadFromStart.
Also there is a preparedstatement left open in
JDBCPersistenceManager$1HandleBeforeCommit1PCRunner.doTransaction(JDBCPersistenceManager.java:1587)
This line creates a prepared statement within a loop but only the last statement created
will be released. Other examples of this construct, within this file, use a simple guard
to prevent subsequent allocations. This appears to be the only occurrence which does
not."
The preparedstatements will be when the connection is closed, but if you process a large
transaction there is a possibility you could run out of resources in your database for
that transaction. E.g. run out of cursors on Oracle.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira