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

Stale Thread error in logs

SA-5713

Summary



Stale Thread error in logs

Error Messages



[12/10/14 9:53:00:314 CST] 0000001c SystemOut     O 2014-12-10 09:53:00,313 [j2ee14_ws,maxpri=10]] [  STANDARD] [                    ] (          mgmt.base.ThreadData) ERROR   - Trying to use a destroyed thread
com.pega.pegarules.pub.context.StaleThreadError: Thread has been destroyed
    at com.pega.pegarules.session.internal.mgmt.base.ThreadData.validateUse(ThreadData.java:551)
    at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.validateUse(PRThreadImpl.java:328)
    at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.getThreadFamilyName(PRThreadImpl.java:1661)
    at com.pega.pegarules.session.internal.mgmt.base.RequestorPageDir.getFamilyPageMapForCurrentThread(RequestorPageDir.java:460)
    at com.pega.pegarules.session.internal.mgmt.base.RequestorPageDir.getPage(RequestorPageDir.java:238)
    at com.pega.pegarules.session.internal.mgmt.base.RequestorPageDir.getPage(RequestorPageDir.java:222)
    at com.pega.pegarules.session.internal.mgmt.base.RequestorPageDir.getRequestorPage(RequestorPageDir.java:275)
    at com.pega.pegarules.session.internal.mgmt.PRRequestorImpl.getRequestorPage(PRRequestorImpl.java:1077)
    at com.pega.pegarules.session.internal.mgmt.base.ThreadPassivation.configureThreadImpl(ThreadPassivation.java:242)
    at com.pega.pegarules.session.internal.mgmt.PRThreadBase.configureThread(PRThreadBase.java:438)
    at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.<init>(PRThreadImpl.java:307)
    at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.acquire(PRThreadImpl.java:318)
............

Steps to Reproduce



NA


Root Cause



The UsageDaemon background thread runs all the time, and this particular thread somehow is getting interfered with normal threads of the user requestors, which is not expected to happen in the happy path scenario. If the daemon ends up using this recycled thread, due to this bug, it uses this thread without properly re-initializing it.
 


Resolution



HFix-20640 is provided.

Published January 31, 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