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

AES reports thread recycle errors - StaleThreadError



AES reports multiple recycled and stale thread exceptions. 

Error Messages

2013-07-29 15:58:58,741 [   WorkManager(2)-75] [  STANDARD] [                    ] (          mgmt.base.ThreadData) ERROR   - Trying to use a destroyed thread Thread has been destroyed

at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.validateUse(
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.getStepStatus(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.invoke(
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(

Steps to Reproduce

Not Applicable

Root Cause

Pegasystems’ code does not protect against attempts to process requestors with a destroyed thread.


This issue is resolved in Pega 7.

Install HFix-7666, HFix-7697, and HFix-7815 for PRPC 6.3 SP1.

Published June 23, 2015 - 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