Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Date: Wed, 11 Jun 2008 18:18:34 +0200
From: Knut Anders Hatlen <Knut.Hatlen@Sun.COM>
Subject: Re: Derby crash (urgent)
In-reply-to: <17778534.post@talk.nabble.com>
Sender: Knut.Hatlen@Sun.COM
To: derby-dev@db.apache.org
Message-id: <wjo83ank2bdx.fsf@khepri41.norway.sun.com>
Organization: Sun Microsystems
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <20080321230438.3CC8572496F@athena.apache.org>
 <16751000.post@talk.nabble.com> <4807ABE8.7000206@Sun.COM>
 <17778534.post@talk.nabble.com>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/22.2 (usg-unix-v)

Bassel_kh <bkhashfeh@hotmail.com> writes:

> Actually, I removed C3P0 totally, and upgraded derby to 10.4, the new
> Exception occured:

Hi,

Did you create a new database after upgrading to Derby 10.4, or did you
continue with an old database created with an earlier version of Derby?
I'm asking this to find out if this is a new bug or a know bug that was
fixed in Derby 10.4. If the database has become corrupted (as we know
could happen with some of the 10.2 and 10.3 releases), upgrading Derby
won't help you accessing that database.

> I got tired of using Derby, It is not that professional, and still not
> stable!!

If it is possible, it would be great if you could post some code to
reproduce the problem. That would be very helpful for those who would
like to track it down and make Derby more stable.

> Also new bug came today: Inconsistent index!!

My guess is that it is probably not a new bug, just a different
manifestation of the same one. Since it seems like your database has
become corrupted, all sorts of errors may happen, and the exact error
message may vary depending on which operation is performed when the
damaged data is accessed.

-- 
Knut Anders