Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

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 [email protected]b (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:
  1. Release the lock.
  2. 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.
Suggest Edit

Published November 3, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us