[DBCP-513] Hundreads of threads in Wait state with below stack trace

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.1.1, 2.6.0
• Fix Version/s: 2.6.0

Environment

Java Version: 

1.8.0_121

 OS Complete Version: 

Linux sdpvvrwm556 3.10.0-693.11.6.el7.x86_64 #1 SMP Thu Dec 28 14:23:39 EST 2017 x86_64 x86_64 x86_64 GNU/Linux

 

DBCP Jar:

commons-dbcp2-2.1.1.jar

• Assignee: Mark Struberg
• Reporter: Mahesh
• Created: 19/Jul/18 13:35
• Updated: 08/Feb/24 13:26
• Resolved: 25/Oct/18 12:54

Description

Hello Team,

Our application suddenly stops responding, when we checked thread dump, most of the threads are in wait state with below stack trace, we had to restart server to make it active, can you pelase provide your inputs on the root cause & resolution?

 

"JSockConn Thread #4532" #40906 prio=5 os_prio=0 tid=0x00007f84382ce800 nid=0xc692 waiting on condition [0x00007f83d38f8000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)

• parking to wait for <0x00000005c30a11b8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
  at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
  at org.apache.commons.pool2.impl.LinkedBlockingDeque.takeFirst(LinkedBlockingDeque.java:583)
  at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:442)
  at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)
  at org.apache.commons.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:134)
  at org.apache.commons.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:1533)

Issue Links

• is blocked by: POOL-356 deadlock if borrowObject gets called to fast and maxIdle is 0
• is related to: DBCP-595 Connection pool can be exhausted when connections are killed on the DB side