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

Unable to restart node

SA-26045

Summary



On attempting to restart a multinode cluster environment, some of the nodes did not restart.

Error Messages



[**Date, time, and time zone**] 000000bb ThreadMonitor W WSVR0605W: Thread "<your_hostname>" (0000008d) has been active
for 696797 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(LockSupport.java:198)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:846)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1006)
.
.
.

Steps to Reproduce

  1. Set up a multinode-Dnode cluster.
  2. Set up a Visual Business Director (VBD) cluster with two nodes.
  3. Restart all nodes.

Root Cause



A defect in Pegasystems’ code or rules. A deadlock can occur when starting multiple VBD nodes concurrently. Two threads compete for a Hazelcast distributed lock when persistence is initialized.

Resolution



Apply HFix-28668.

Published August 5, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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