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 (nike.apache.org: domain of blair@orcaware.com designates
 12.11.234.124 as permitted sender)
Message-ID: <4980ABB1.6050107@orcaware.com>
Date: Wed, 28 Jan 2009 11:02:09 -0800
From: Blair Zajac <blair@orcaware.com>
User-Agent: Thunderbird 1.5.0.14ubu (X11/20090105)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: 50 transactions timing out with no CPU usage and no deadlocks
References: <497D1184.8020301@orcaware.com> <497D7586.90002@Sun.COM>
 <497E4919.7090908@orcaware.com> <x6wscgon3l.fsf@Sun.COM>
In-Reply-To: <x6wscgon3l.fsf@Sun.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Knut Anders Hatlen wrote:
> Blair Zajac <blair@orcaware.com> writes:
> 
>> I downloaded d2991-preview-1e.diff and applied it to r737572 of trunk.
>> I don't see the original problem now.  Even going to 500 threads and
>> setting derby.locks.waitTimeout to -1 works.
>>
>> Will or when will a patch for d2991 be applied to trunk?
> 
> Thanks for testing the patch. A patch for DERBY-2991 will hopefully make
> it into the upcoming Derby 10.5.1 release
> (http://wiki.apache.org/db-derby/DerbyTenFiveOneRelease). Currently,
> we're evaluating the performance impact of the suggested fix.

Thanks.  What kind of performance impact does the patch have on Derby?

To be half joking and half series, without the fix, the performance of my app 
goes to 0 when the application runs into this issue.

Blair