On 14/01/2010, contin...@vmbuild.apache.org wrote:
> Online report :
> http://vmbuild.apache.org/continuum/buildResult.action?buildId=269640&projectId=22
>
>
> Build statistics:
> State: Failed
> Previous State: Failed
>
> Started at: Thu 14 Jan 2010 06:05:51 -0800
> Finished at: Thu 14
Looks like the Thread.sleep(100L) is taking too long, and allowing
some of the initial 10 threads to complete their hold time; this
accounts for the threads with more than 1 loop.
However, the last 10 threads should still timeout, as none of the
first 10 threads should release the connection until
That's strange - same symptoms as DBCP-318, but this time it affects
both TestPerUserPoolDataSource and TestSharedPoolDataSource so it must
be a different bug, as 318 only affected PerUser.
I've not yet tried soak testing using Java 1.5; I hope to find time to
do so later today.
Meanwhile I will
It seems there are further failure modes ;-)
I'm intending to update the test case to provide further information
on how the threads behave.
On 02/01/2010, contin...@vmbuild.apache.org wrote:
> Online report :
> http://vmbuild.apache.org/continuum/buildResult.action?buildId=265454&projectId=22
On Wed, Jan 14, 2009 at 5:49 PM, Mark Thomas wrote:
>> From: contin...@vmbuild.apache.org [mailto:contin...@apache.org]
>> Sent: 14 January 2009 22:30
>> To: dev@commons.apache.org
>> Subject: [continuum] BUILD FAILURE: Commons - Commons DBCP -
>
> I'd like to fix whatever is causing this but when
> From: contin...@vmbuild.apache.org [mailto:contin...@apache.org]
> Sent: 14 January 2009 22:30
> To: dev@commons.apache.org
> Subject: [continuum] BUILD FAILURE: Commons - Commons DBCP -
I'd like to fix whatever is causing this but when I try an look at the
continuum server I get either "Project
