[
https://issues.apache.org/jira/browse/DERBY-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172049#comment-14172049
]
Mamta A. Satoor commented on DERBY-6068:
----------------------------------------
The 32K limit is imposed by maxNumSections field in
org.apache.derby.client.am.SectionManager. I researched this further and found
that this limit is dictated by DRDA specification in Volumn 1: Distributed
Relational Database Architecture (DRDA). It is covered under SQL Section Number
Assignment (SN Rules) on page 489 as copied below
SN1 A section number is between 1 and 32,767 inclusive.
Based on this, I do not believe we can increase the limit on section numbers.
In the past we had run into one issue because of this limitation DERBY-6054 but
it was possible to tweak customer's environment to avoid this limitation. Other
than that case, I do not think we have run into any issues because of 32K
limit. I will close this jira as won't fix. Please let me know if my
understanding of the spec is not correct.
> Increase the arbitrary 32K limit imposed by DRDA on number of Sections used
> for open statements
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-6068
> URL: https://issues.apache.org/jira/browse/DERBY-6068
> Project: Derby
> Issue Type: Improvement
> Components: Network Server
> Affects Versions: 10.10.1.1
> Reporter: Mamta A. Satoor
> Assignee: Mamta A. Satoor
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
