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 (athena.apache.org: local policy)
Date: Tue, 27 Jan 2009 15:57:46 +0100
From: Kristian Waagan <Kristian.Waagan@Sun.COM>
Subject: Re: 50 transactions timing out with no CPU usage and no deadlocks
In-reply-to: <497E4919.7090908@orcaware.com>
Sender: Kristian.Waagan@Sun.COM
To: Derby Discussion <derby-user@db.apache.org>
Message-id: <497F20EA.8070002@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <497D1184.8020301@orcaware.com> <497D7586.90002@Sun.COM>
 <497E4919.7090908@orcaware.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20081203)

Blair Zajac wrote:
> Kristian Waagan wrote:
>> Blair Zajac wrote:
>>>
>> Hello Blair,
>>
>> My only *guess* is that there might be a restructuring of a BTree 
>> going on, which is not correctly reported - and you might be 
>> experiencing a deadlock. To stop guessing and actually start 
>> understanding what's going on, it would be great if you could provide 
>> a standalone repro.
>> Such a repro is best handled by creating a bug report in Jira:
>> https://issues.apache.org/jira/browse/DERBY
> 
> Hello Kristian,
> 
> Thanks for the quick reply.
> 
> I do have a reproduction standalone Java file that runs the tests.  I've 
> attached it to the note.  Should I still open a ticket if the DERBY-2991 
> patch works?

Feel free to open a ticket anyway. It makes it easier for the community 
to track the issue.


Regards,
-- 
Kristian

> 
> More information below.
> 
>

[ snip ]