Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-dev@maven.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <44B062A2.7010903@apache.org>
Date: Sun, 09 Jul 2006 03:57:54 +0200
From: =?ISO-8859-1?Q?Trygve_Laugst=F8l?= <trygvis@apache.org>
User-Agent: Thunderbird 1.5.0.4 (X11/20060619)
MIME-Version: 1.0
To: continuum-dev@maven.apache.org
Subject: Re: introduction
References: <1152377023.44afe0bf7ec22@webmail.jpox.org>
 <44AFFC51.3090804@venisse.net>
In-Reply-To: <44AFFC51.3090804@venisse.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Emmanuel Venisse wrote:
> Thanks Erik.
> 
> In Continuum, we use jpox with derby. Lot of users get some exception 
> with them on requests that failed like foreign key violation, 
> insert/delete errors, deadlock errors...
> 
> Our problem is this errors doesn't appears all the time and it's very 
> difficult to reproduce them. I'm not sure (but I think) errors are in 
> jpox and not in derby. I know deadlock lock and timeout lock are fixed 
> in the new derby version and we'll update it.

Another issue I would like to figure out is why jpox+derby is using 
exactly 2.0 minutes to start up.

Thanks for starting this effort, we've been really close to dumping jpox 
unless we get some help to figure out our issues with it.

--
Trygve