commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <>
Subject [jira] [Commented] (POOL-230) waiting on <0x00000000e7440168> (a org.apache.commons.pool.impl.GenericObjectPool$Latch)
Date Mon, 24 Sep 2012 16:58:08 GMT


Phil Steitz commented on POOL-230:

Looks like normal behavior to me when the pool is configured to block when exhausted and there
are no instances available in the pool.  The thread is executing a timed wait, waiting for
an instance to become available.  This does not look related to POOL-149 to me.
> waiting on <0x00000000e7440168> (a org.apache.commons.pool.impl.GenericObjectPool$Latch)
> ----------------------------------------------------------------------------------------
>                 Key: POOL-230
>                 URL:
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 1.5.4
>         Environment: tomcat using dbcp
>            Reporter: jerrybi
> "Thread-20" daemon prio=10 tid=0x00007f5810214000 nid=0x5f7b in Object.wait() [0x00007f581527c000]
>    java.lang.Thread.State: TIMED_WAITING (on object monitor)
> 	at java.lang.Object.wait(Native Method)
> 	- waiting on <0x00000000e7440168> (a org.apache.commons.pool.impl.GenericObjectPool$Latch)
> 	at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(
> 	- locked <0x00000000e7440168> (a org.apache.commons.pool.impl.GenericObjectPool$Latch)
> 	at org.apache.commons.dbcp.PoolingDataSource.getConnection(
> 	at org.apache.commons.dbcp.BasicDataSource.getConnection(
> it seems that the problem bellow still exits. 
> I am using commons-dbcp-1.3 and commons-pool-1.5.4

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message