Using setQueryTimeout will leak sections
-----------------------------------------
Key: DERBY-3198
URL: https://issues.apache.org/jira/browse/DERBY-3198
Project: Derby
Issue Type: Bug
Components: JDBC, Network Client
Affects Versions: 10.3.1.4
Reporter: Dyre Tjeldvoll
The implementation of setQueryTimeout relies on
NetStatementReply.writeSetSpecialRegister() which will allocate a dynamic
section when called. No reference to this Section object is kept, and so
Section.free() never gets called on it. Executing the same statment repeatedly
with a query timeout set results in the client driver throwing an exception
because the number of Sections exceeding 32000.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
