Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
10.10.1.1
-
None
-
None
Description
We recommend users to close the statements ResultSet.getStatement().close() to make sure the statements get closed. But it would help us to increase the limit of 32K on open statements in case a machine is slow and gargbage collection is not happening fast enough. One instance where we ran into this 32K limit violation is DERBY-6054.
Attachments
Issue Links
- relates to
-
DERBY-6054 java.sql.SQLException: Exceeded maximum number of sections 32k in application with many setTransactionIsolation statements
- Closed