Support Article
Thread Deadlock issue affecting performance
SA-48067
Summary
Thread deadlock affects performance.
Error Messages
Instance_1_9ed2c8728883b6127c59003f8efca5b1.event-3" Id=284 in WAITING on lock=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@629f33fc
BlockedCount : 166, BlockedTime : -1, WaitedCount : 178, WaitedTime : -1
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
at com.hazelcast.util.executor.StripedExecutor$Worker.run(StripedExecutor.java:173)
Steps to Reproduce
Unknown
Root Cause
A defect in Pegasystems’ code or rules. There is a deadlock between the Aggregate Spend Management (ASM) and the cluster.
Resolution
Apply HFix-39713.
Published December 30, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.