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.