Support Article
Thread dumps reveal long running report
SA-20162
Summary
Thread dumps in logs show long-running processes relating to reporting.
Error Messages
In the hung threads the lock was held by the below thread;
"WebContainer : 17" Id=175646 in WAITING on lock=java.util.concurrent.locks.ReentrantLock$NonfairSync@8a1113b (running in
native)
BlockedCount : 67, BlockedTime : -1, WaitedCount : 277930, WaitedTime : -1
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:197)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:845)
Steps to Reproduce
Unknown
Root Cause
A defect in Pegasystems’ code or rules:
There is a race condition where one thread has finished loading the page and performs the following:
- Release the lock.
- Insert the page in directory.
As soon as it releases the lock, the other thread grabs this lock and searches the page in directory. It does not find any, however, because the PUT operation has been completed yet by First Thread. Thus, it tries to reload the same page again and succeeds.
Resolution
Apply HFix-24551.
Published November 3, 2016 - 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.