Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 11 Feb 2013 18:31:14 +0000 (UTC)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12631769.1360607424211.273977.1360607474888@arcas>
In-Reply-To: <JIRA.12631769.1360607424211@arcas>
References: <JIRA.12631769.1360607424211@arcas>
Subject: [jira] [Created] (DERBY-6068) Increase the arbitrary 32K limit
 imposed by DRDA on number of Sections used for open statements
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Mamta A. Satoor created DERBY-6068:
--------------------------------------

             Summary: 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.0.0
            Reporter: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira