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

Exception while gathering usage data

SA-6006

Summary



The below warning is observed in  log files. Users would like to know the reason behind the same. 

20:04:00,042 [egaRULES UsageDaemon] (nitor.internal.UsageDaemonImpl) WARN - Exception while gathering usage data, ignoring requestor AA6FFDC0A1D1B25BD9D15B6F9FEECE2CA
java.lang.NullPointerException
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:928)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:804)
at com.pega.pegarules.monitor.internal.UsageDaemonImpl.snapshotAllRequestors(UsageDaemonImpl.java:1102)
at com.pega.pegarules.monitor.internal.UsageDaemonImpl.processUsageData(UsageDaemonImpl.java:808)
at sun.reflect.GeneratedMethodAccessor369.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1092)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:771)
at com.pega.pegarules.monitor.internal.UsageDaemonImpl.processData(UsageDaemonImpl.java:736)
at com.pega.pegarules.monitor.internal.UsageDaemonImpl.run(UsageDaemonImpl.java:664)
at java.lang.Thread.run(Thread.java:662)


Error Messages



Not Applicable.


Steps to Reproduce



No specific use case available. This scenario happens sporadically.

Root Cause



The usage daemon (thread) tries to collect information regarding the other requestors. 

Refer: https://pdn.pega.com/sites/default/files/help_v71/procomhelpmain.htm#definitions/u/usagedaemon.htm

In case the requestor is not valid or has some authorization issue, the usage daemon is not able to gather information for that requestor. All the recognizable/important use cases are already handled in the code (like, Stalerequestor, stalethread, requestorlock). For other cases, Warning is logged in the logs and usage daemon will continue other processing. 


Resolution



This is just the usage daemon logging information regarding the requestor in the log-usage. It is a warning and does not affect any functionality. 

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