[continuum] BUILD FAILURE: Commons - Commons DBCP - Try debug build

2010-01-13 Thread contin...@vmbuild.apache.org
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=269449&projectId=22 Build statistics: State: Failed Previous State: Failed Started at: Wed 13 Jan 2010 22:51:10 -0800 Finished at: Wed 13 Jan 2010 22:52:46 -0800 Total time: 1m 36s Build Trigger: Schedule

[continuum] BUILD FAILURE: Commons - Commons DBCP - Try debug build

2010-01-13 Thread contin...@vmbuild.apache.org
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=269381&projectId=22 Build statistics: State: Failed Previous State: Ok Started at: Wed 13 Jan 2010 20:33:52 -0800 Finished at: Wed 13 Jan 2010 20:35:24 -0800 Total time: 1m 31s Build Trigger: Schedule Bui

Re: [DBCP] Odd code in SharedPoolDataSource.getPooledConnectionAndInfo()

2010-01-13 Thread Phil Steitz
sebb wrote: > The method SharedPoolDataSource.getPooledConnectionAndInfo has the > following code: > > synchronized (userKeys) { > if (userKeys.containsKey(username)) { > userKeys.remove(username); > } > } > > Why not jus

[DBCP] Odd code in SharedPoolDataSource.getPooledConnectionAndInfo()

2010-01-13 Thread sebb
The method SharedPoolDataSource.getPooledConnectionAndInfo has the following code: synchronized (userKeys) { if (userKeys.containsKey(username)) { userKeys.remove(username); } } Why not just use userKeys.remove(username)?

Re: [DBCP] Continuum failure - discussion of timings

2010-01-13 Thread sebb
On 13/01/2010, sebb wrote: > On 13/01/2010, sebb wrote: > > On 13/01/2010, sebb wrote: > > > Here is the output from > > > > http://vmbuild.apache.org/continuum/buildResult.action?buildId=268733&projectId=22 > > > > > > I've rearranged it so the threads are in ConnectionStart order.

[continuum] BUILD SUCCESSFUL: Commons - Commons DBCP - Try debug build

2010-01-13 Thread contin...@vmbuild.apache.org
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=269278&projectId=22 Build statistics: State: Ok Previous State: Failed Started at: Wed 13 Jan 2010 15:23:03 -0800 Finished at: Wed 13 Jan 2010 15:24:43 -0800 Total time: 1m 40s Build Trigger: Schedule Bui

[continuum] BUILD FAILURE: Commons - Commons DBCP - Try debug build

2010-01-13 Thread contin...@vmbuild.apache.org
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=269236&projectId=22 Build statistics: State: Failed Previous State: Failed Started at: Wed 13 Jan 2010 14:03:24 -0800 Finished at: Wed 13 Jan 2010 14:04:40 -0800 Total time: 1m 15s Build Trigger: Schedule

[continuum] BUILD FAILURE: Commons - Commons DBCP - Try debug build

2010-01-13 Thread contin...@vmbuild.apache.org
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=269201&projectId=22 Build statistics: State: Failed Previous State: Ok Started at: Wed 13 Jan 2010 12:57:32 -0800 Finished at: Wed 13 Jan 2010 12:58:57 -0800 Total time: 1m 24s Build Trigger: Schedule Bui

Re: [DAEMON] New release of daemon?

2010-01-13 Thread Kevan Miller
On Jan 13, 2010, at 12:04 AM, Mladen Turk wrote: > On 01/12/2010 05:17 PM, Jack Cai wrote: >> >> I also reported a bunch of JIRAs against procrun and provided >> corresponding fixes, back to a year ago. Can we also make a new >> procrun release? >> > > Sure, it'll be part of that release. > I

Re: [DBCP] Continuum failure - discussion of timings

2010-01-13 Thread sebb
On 13/01/2010, sebb wrote: > On 13/01/2010, sebb wrote: > > Here is the output from > > > http://vmbuild.apache.org/continuum/buildResult.action?buildId=268733&projectId=22 > > > > I've rearranged it so the threads are in ConnectionStart order. > > I moved ConnectionStart to the beginnin

[continuum] BUILD SUCCESSFUL: Commons - Commons DBCP - Try debug build

2010-01-13 Thread contin...@vmbuild.apache.org
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=269069&projectId=22 Build statistics: State: Ok Previous State: Failed Started at: Wed 13 Jan 2010 07:31:21 -0800 Finished at: Wed 13 Jan 2010 07:32:41 -0800 Total time: 1m 20s Build Trigger: Schedule Bui

[continuum] BUILD FAILURE: Commons - Commons DBCP - Try debug build

2010-01-13 Thread contin...@vmbuild.apache.org
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=269039&projectId=22 Build statistics: State: Failed Previous State: Ok Started at: Wed 13 Jan 2010 06:18:53 -0800 Finished at: Wed 13 Jan 2010 06:20:47 -0800 Total time: 1m 53s Build Trigger: Schedule Bui

[pool] excessive synch scope when checking for allocated latches?

2010-01-13 Thread Phil Steitz
GOP and GKOP both use the following idiom in several places to check to see if an instance has been allocated to a thread: synchronized (this) { // Make sure allocate hasn't already assigned an object // in a different thread or permitted a new object to be created if (latch.getPair() == null

Re: [DBCP] Continuum failure - discussion of timings

2010-01-13 Thread Phil Steitz
sebb wrote: > Here is the output from > http://vmbuild.apache.org/continuum/buildResult.action?buildId=268733&projectId=22 > > I've rearranged it so the threads are in ConnectionStart order. > I moved ConnectionStart to the beginning, added the Thread number at > the end (dropping irrelevant stuff

Re: [DBCP] Continuum failure - discussion of timings

2010-01-13 Thread sebb
On 13/01/2010, sebb wrote: > Here is the output from > > http://vmbuild.apache.org/continuum/buildResult.action?buildId=268733&projectId=22 > > I've rearranged it so the threads are in ConnectionStart order. > I moved ConnectionStart to the beginning, added the Thread number at > the end (dro

[continuum] BUILD SUCCESSFUL: Commons - Commons DBCP - Try debug build

2010-01-13 Thread contin...@vmbuild.apache.org
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=268984&projectId=22 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed 13 Jan 2010 03:31:32 -0800 Finished at: Wed 13 Jan 2010 03:33:20 -0800 Total time: 1m 48s Build Trigger: Sc