[
https://issues.apache.org/jira/browse/DERBY-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543087
]
Dyre Tjeldvoll commented on DERBY-3198:
---------------------------------------
I have now had a chance to look at DERBY-1848, but I don't think these issues
are directly related. The Section issue will only occur when using the client
driver, and exhausting the number of Sections produces a specific error message
and call stack which I don't see in DERBY-1848. Based on the diff shown there,
it seems like a statement times out unexpectedly, which I guess could happen if
you happen to get a full GC (or other delay) at the wrong time.
> 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
> Attachments: repro.diff
>
>
> 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.
