Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-users@maven.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <47065B10.4040205@venisse.net>
Date: Fri, 05 Oct 2007 17:41:04 +0200
From: Emmanuel Venisse <emmanuel@venisse.net>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: continuum-users@maven.apache.org
Subject: Re: 1.1-beta-3 crashes and corrupts database ?
References: <20071005133412.GD8823@mars.cry.pto>
 <4706409F.8010303@venisse.net> <20071005144828.GF8823@mars.cry.pto>
In-Reply-To: <20071005144828.GF8823@mars.cry.pto>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

I don't know why sequence aren't updated correctly by jpox, probably because when the tool import datas, it use object IDs from the xml file so jpox don't know it need to update the NEXT_VAL

Emmanuel

Julien Stern a �crit :
> On Fri, Oct 05, 2007 at 03:48:15PM +0200, Emmanuel Venisse wrote:
>> I think it's a problem with NEXT_VAL values in SEQUENCE_TABLE. Look at the 
>> end of 
>> http://maven.apache.org/continuum/guides/mini/guide-data-management.html 
>> for informations.
> 
> Many thanks for the link. It took a bit of time as the server is
> headless, but it now works again.
> 
> However, I believe there is a fairly major bug that needs to be fixed.
> Indeed, the error did not occur after an import, but simply during
> the normal course of continuum...
> 
> Well, to be quite precise, if you're interested, here is what happened:
> 
> 1) I imported the continuum db from beta-2 with the data mngt tool
> 2) I started beta-3 (no problem)
> 3) It ran for a week or so
> 4) It crashed for some unknown reason
> 5) It would not restart because of this db problem
> 
> So, maybe the DB was corrupted from step 1, but if that is not the case,
> there is a big problem :)
> 
> Regards,
> 
> --
> Julien
> 
>> Emmanuel
>>
>> Julien Stern a �crit :
>>> Hi list,
>>>
>>> Our continumm 1.1-beta-3 had been running smoothly for several weeks,
>>> and this morning it crashed, apparently attempted to automatically
>>> restart and failed because of an SQL Error.
>>>
>>> I've stopped it, but now it does not restart.
>>>
>>> I've attached a stack trace. Any help would be highly appreciated
>>> as we cannot restart continumm at present.
>>>
>>> Regards,
>>>
>>> --
>>> Julien
>>>
> 
>