Question

8
Replies
3564
Views
Surya_INCESSANT Member since 2013 1 post
Incessant Technologies
Posted: July 23, 2016
Last activity: January 17, 2017
Closed

Thread Dump is happening due to java.util.concurrent.SynchronousQueue$TransferStack

Please let us know someone had facced the similar issue.

2016-06-23 19:55:34,133 [XX.XXX.XX.XX:8447-8] [          ] [                    ] (.timers.EnvironmentDiagnostics) INFO  bfssyddev155-vip1|XX.XX.XX.XX  - --- Thread Dump Starts ---
Full Java thread dump with locks info
"pool-2-thread-39" Id=4156 in TIMED_WAITING on lock=java.util.concurrent.SynchronousQueue$TransferStack@45f68ee7
BlockedCount : 3, BlockedTime : -1, WaitedCount : 6, WaitedTime : -1
    at sun.misc.Unsafe.park(Native Method)
    at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
    at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
    at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:359)
    at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:942)
    at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)

    Locked synchronizers: count = 0

 

Please let us know someone had facced the similar issue.

***Updated by moderator: Lochan to add Category***

System Administration
Moderation Team has archived post
Share this page LinkedIn