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
We do a *lot* of testing, including long-running tests and large
database size tests. We're trying to add more and more tests,
robustness and compatibility are key goals for many of us on this team.
If you really need a production-level support, you should probably go
through Sun (Java DB)
-Original Message-
From: David W. Van Couvering [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:54 AM
To: Derby Discussion
Subject: Re: embedded derby -- does it leak
We do a *lot* of testing, including long-running tests and large
database size tests. We're
: embedded derby -- does it leak
We do a *lot* of testing, including long-running tests and large
database size tests. We're trying to add more and more tests,
robustness and compatibility are key goals for many of us on this team.
If you really need a production-level support, you should
PROTECTED]
Sent: Tuesday, February 14, 2006
9:00 PM
To: Derby Discussion
Subject: Re: embedded derby --
does it leak
Jim
Newsham [EMAIL PROTECTED] wrote:
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
is reported as fixed while 912 is still open. Is 912 expected to be fixed by v10.2 also?Thanks, Jim NewshamFrom: Rajesh Kartha [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 14, 2006 9:00 PMTo: Derby DiscussionSubject: Re: embedded derby -- does i
t
leakJim Newsham [EMAIL
'
Subject: RE: embedded derby -- does it leak
Michael,
Thank you for your reply. With all due respect, I don't feel that users
of
a database should assume that there will be memory leaks.
I appreciate that Derby is an open source project, nevertheless it is a
database product
Jim Newsham wrote:
Are there other
outstanding memory/leak related bugs which I'm not aware of? Would you
recommend Derby for my project?
With embedded there is an issue in 10.1,
https://issues.apache.org/jira/browse/DERBY-599
This bug is related to large objects getting materialized and
Mike,
Thanks for the clarification. We are in agreement.
The key is to identify the reported bugs and consider the following
metrics:
1) The severity of the bug. (Factor in the frequency and conditions that
caused the bug to pop up)
2) Time from Bug reporting to when it was
] wrote:
-Original Message-
From: David W. Van Couvering [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:54 AM
To: Derby Discussion
Subject: Re: embedded derby -- does it leak
We do a *lot* of testing, including long-running tests and large
database size tests. We're trying
Jim Newsham [EMAIL PROTECTED] wrote:
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.
Is there a way to get more details on what type of
11 matches
Mail list logo
