Support Article

Hung threads on LocalizedApplicationContext.getChangeCount()



The Java Virtual Machine (JVM) experienced hung threads.

Error Messages

[**Date, time, and time zone**] 00000003 ThreadMonitor W   WSVR0605W: Thread "WebContainer : 50" (000000aa) has been active for 613538 milliseconds and may be hung.  There is/are 1 thread(s) in total in the
server that may be hung.
    at sun.misc.Unsafe.park(Native Method)
    at java.util.concurrent.locks.LockSupport.park(
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(

Steps to Reproduce


Root Cause

A defect in Pegasystems’ code or rules. This deadlock is a known edge condition, which can occur under load during Application Context getChangeCount locking.


Apply HFix-29540.

Published September 27, 2016 - Updated October 6, 2016

Have a question? Get answers now.

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