You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Abhishek Rao (JIRA)" <ji...@apache.org> on 2018/12/24 03:26:00 UTC
[jira] [Commented] (DBCP-513) Hundreads of threads in Wait state
with below stack trace
[ https://issues.apache.org/jira/browse/DBCP-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728116#comment-16728116 ]
Abhishek Rao commented on DBCP-513:
-----------------------------------
We're facing a similar problem with SharedPoolDataSource. At one point a lot of BLOCKED threads are seen because the pool exhausts due to a sudden surge in connection requests. Following this there's a pattern repeating itself and response times go haywire in our application. The surge / exhaustion is not backed up by a slow database or anything like that, and we have done a whole lot of analysis on our databases (Oracle RAC) and found that service times are around 2-4ms max! I've upgraded DBCP to the latest master and commons pool 2.6.1 and still seeing this issue.
!image-2018-12-24-08-54-06-625.png!
> Hundreads of threads in Wait state with below stack trace
> ---------------------------------------------------------
>
> Key: DBCP-513
> URL: https://issues.apache.org/jira/browse/DBCP-513
> Project: Commons DBCP
> Issue Type: Bug
> Affects Versions: 2.1.1, 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
> Reporter: Mahesh
> Assignee: Mark Struberg
> Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: Screen Shot 2018-08-05 at 10.29.52 AM.png, dbcp_lock_1.txt, dbcp_lock_7.txt, dbcpthread.zip, image-2018-12-24-08-42-34-611.png, image-2018-12-24-08-45-09-224.png, image-2018-12-24-08-54-06-625.png
>
>
> 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)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)