Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
From: Michael Segel <derby@segel.com>
Reply-To: derby@segel.com
Organization: MSCC 
To: "Derby Discussion" <derby-user@db.apache.org>
Subject: Re: embedded derby -- does it leak
Date: Wed, 15 Feb 2006 10:01:04 -0600
User-Agent: KMail/1.8.2
References: <001201c631de$eee45540$6f00a8c0@referentia.com>
In-Reply-To: <001201c631de$eee45540$6f00a8c0@referentia.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200602151001.04166.derby@segel.com>

On Tuesday 14 February 2006 9:21 pm, Jim Newsham wrote:

Jim,

Assume that there will be memory leaks.

No code is perfect, and there may be memory leaks not just in Derby, but the 
JVM implementation that you are using, or the JDBC drivers.

This isn't limited to Derby. Other Open Source as well as commercial programs 
are going to be prone to leakage.

> Hi,
>
>
>
> We need to include a database along with our Java-based desktop
> application, and for deployment/maintenance reasons, an embedded database
> would be ideal. I'm evaluating whether derby will suit our needs, and so
> far I really like what I see.  However, some colleagues have told me that
> they had evaluated derby in the past (a few months ago), and that they
> passed on it after seeing memory leak problems which resulted in
> OutOfMemoryException.  The application may need to run for a long time, and
> may generate a very large amount of data, therefore, a recurring memory
> leak is a showstopper.  I wanted to give Derby another look before moving
> on.
>
>
>
> I looked through JIRA to try to identify bugs related to memory leaks.  I
> found:
>
>
>
> DERBY-756 (fixed; reported against 10.1.2.1, but doesn't say which version
> the fix is applied to)
>
> DERBY-912
>
>
>
> I skipped over these because they appear to be client/server (please
> correct me if I'm wrong):
>
>
>
> DERBY-210
>
> DERBY-557
>
>
>
> I also browsed the derby-user list, but didn't find anything substantive.
> So, on to my questions:
>
>
>
> How stable, robust, and well-tested is derby?  How often do critical bugs
> find their way into production releases (please include "memory leaks" in
> the definition of critical)?  How long does it take for bugs such as the
> above to make their way into a production release, and when could I
> reasonably expect these two to be available for production?  Are there
> other outstanding memory/leak related bugs which I'm not aware of?  Would
> you recommend Derby for my project?
>
>
>
> Thanks,
>
>
>
> Jim Newsham

-- 
--
Michael Segel
Principal 
Michael Segel Consulting Corp.
derby@segel.com
(312) 952-8175 [mobile]