Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2040819235.1213107885105.JavaMail.jira@brutus>
Date: Tue, 10 Jun 2008 07:24:45 -0700 (PDT)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3713) memory leak when insert rows into a
 table using org.apache.derby.jdbc.EmbeddedDriver
In-Reply-To: <349135845.1212721365086.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-3713:
---------------------------------

    Priority: Major  (was: Critical)
     Urgency: Normal  (was: Urgent)

I am downgrading the urgency and priority of this JIRA because, as Bryan notes, the behavior seems to be what we expect and the behavior can be adjusted by tuning Derby properties.

> memory leak when insert rows into a table using org.apache.derby.jdbc.EmbeddedDriver 
> -------------------------------------------------------------------------------------
>
>                 Key: DERBY-3713
>                 URL: https://issues.apache.org/jira/browse/DERBY-3713
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.4.1.3
>         Environment: solaris and macos,  jdk1.5
>            Reporter: Peter Schi
>
> I downloaded the latest derby and I only modified the SimpleApp.java which came with the software under db-derby-10.4.1.3-bin/demo/programs/simple  directory by inserting a larger string into the same table and I inserted the same data for 10000 times, just using the default driver which was org.apache.derby.jdbc.EmbeddedDriver 
> I found out that there was memory leak, the size of used memory got increased and was about the same size of total data inserted into the table.
> For example, if  2MB size of data was inserted into the table, then the size of used memory was increased by 2MB as well.
> The memory leak still happened even if the database was shut down.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.