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

JMS Listener hangs due to blocking sessions on database



Error is generated in the SystemOut logs while the JMS listener is running. As a result, the requestor thread hangs and stops the Listener pooling.

Error Messages

00000046 ThreadMonitor W WSVR0605W: Thread "MessageListenerThreadPool : 0" (00000111) has been active for 761216 milliseconds and may be hung. There is/are 2 thread(s) in total in the server

Steps to Reproduce

Not Applicable

Root Cause

Blocking sessions occurred on the pr_assembledclasses.

SELECT pzlastmodifiedpzbinarycontent
  FROM PAL_RULES.pr_assembledclasses
WHERE     (pzpackage = :1 OR pzpackage = :2)
       AND pzclass = :3
       AND pzjar = :4
       AND pzCacheConfigId = :5
       AND pzGenerationDate = :6


Apply HFix-44604.

Published August 19, 2019 - 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