[DERBY-3198] Using setQueryTimeout will leak sections

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.4.1.3
• Component/s: JDBC, Network Client
• Assignee: Dyre Tjeldvoll
• Reporter: Dyre Tjeldvoll
• Created: 11/Nov/07 21:53
• Updated: 02/May/13 02:29
• Resolved: 08/Dec/07 16:23

Description

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.

Issue Links

• is depended upon by: DERBY-3192 Cache session data in the client driver
• is related to: DERBY-5524 Speed up clean-up after StatementJdbc30Test.xtestMaxOpenStatementsWithQueryTimeout