Troubleshooting
Problem
Attempts to utilize IBM Rational Team Concert under a high user load resultes in lock contention in the JDBC connection pool.
Symptom
The lock contention in the JDBC Connection pool may render as the inability to connect to the database from the Web UI or evident in the log files, or performance issues from a users perspective.
In the javacore log, many threads are showing up blocked at the following location:
at sun/misc/Unsafe.park(Native Method)
at java/util/concurrent/locks/LockSupport.park(LockSupport.java:182(Compiled Code))
at java/util/concurrent/locks/AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:822(Compiled Code))
at java/util/concurrent/locks/AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:853(Compiled Code))
at java/util/concurrent/locks/AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1189(Compiled Code))
at java/util/concurrent/locks/ReentrantLock$FairSync.lock(ReentrantLock.java:212(Compiled Code))
at java/util/concurrent/locks/ReentrantLock.lock(ReentrantLock.java:273(Compiled Code))
at java/util/concurrent/ArrayBlockingQueue.offer(ArrayBlockingQueue.java:233(Compiled Code))
at com/ibm/team/repository/service/internal/rdb/AbstractPool.releaseEntry(AbstractPool.java:150(Compiled Code))
at com/ibm/team/repository/service/internal/rdb/JDBCConnectionPool.releaseConnection(JDBCConnectionPool.java:220(Compiled Code))
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21646478