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

Static content error

SA-20867

Summary



 Repeating static content error can be seen in the logs.

"2016-03-02 11:41:46,035 [0.134.155.101:8443-6] [ ] [ ] [ ] (tent.StaticContentResolverImpl) ERROR - Caught unhandled error in StaticContentResolver handling request aInput = {};com.pega.pegarules.pub.PRRuntimeException: doWithRequestorOrThreadLocked could not obtain requestor instance from HCA84B889BCE9B8AFF64335111CF018B6; at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorOrThreadLocked(PRSessionProviderImpl.java:2135); at com.pega.pegarules.exec.internal.basic.staticcontent.StaticContentResolverImpl.getRequestorHashInfomation(StaticContentResolverImpl.java:674); at com.pega.pegarules.exec.internal.basic.staticcontent.StaticContentResolverImpl.processRequest(StaticContentResolverImpl.java:605); at com.pega.pegarules.exec.internal.basic.staticcontent.StaticContentResolverImpl.processRequest(StaticContentResolverImpl.java:497); at


Error Messages



"2016-03-02 11:41:46,035 [0.134.155.101:8443-6] [ ] [ ] [ ] (tent.StaticContentResolverImpl) ERROR - Caught unhandled error in StaticContentResolver handling request aInput = {};com.pega.pegarules.pub.PRRuntimeException: doWithRequestorOrThreadLocked could not obtain requestor instance from HCA84B889BCE9B8AFF64335111CF018B6; at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorOrThreadLocked(PRSessionProviderImpl.java:2135); at com.pega.pegarules.exec.internal.basic.staticcontent.StaticContentResolverImpl.getRequestorHashInfomation(StaticContentResolverImpl.java:674); at com.pega.pegarules.exec.internal.basic.staticcontent.StaticContentResolverImpl.processRequest(StaticContentResolverImpl.java:605); at com.pega.pegarules.exec.internal.basic.staticcontent.StaticContentResolverImpl.processRequest(StaticContentResolverImpl.java:497); at
 

Root Cause



When User access the stale session for any Static Content data, We can observe that the logs are filled with doWithRequestorLocked Exceptions. In prpc engine code instead of determining to log the valid exception or not we are directly doing printStackTrace on the exception object which resulted in filling up of the logs in user's PRPC logs.

Resolution



In PRPC engine code(com.pega.pegarules.exec.internal.basic.staticcontent.StaticContentResolverImpl.getRequestorHashInfomation(HashMap, String)) for a stale Requestor id. For a destroyed session if any static content request is fired , we are catching the PRRuntimeException and determining whether it is doWithRequestorLocked Excpetion and logging a warning statement instead throwing it out which results in printStackTrace.

 

Suggest Edit

Published March 14, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

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.

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