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

JMS Listener generating many authentication errors in logs

SA-3285

Summary



Developerts have configured a JMS listener and found that it is generating a huge amount of log errors. This seems to be occurring because there are out-of-the-box (OOTB) final rules which require authentication. Other than the log errors, the JMS listener is working as expected.

Error Messages



2014-10-23 09:22:37,951 [j2ee14_ws,maxpri=10]] [ STANDARD] [ App:01.01.01] ( internal.mgmt.Executable) ERROR .ERMS_JMSListener|JMS|----|Services|----|A0AE80A6FC98A18E02F7A6768229FBFE0 - Only authenticated client may start this activity: RULE-OBJ-ACTIVITY RULE-OBJ-REPORT-DEFINITION PXRETRIEVEREPORTDATA #20140127T063059.806 GMT
com.pega.pegarules.pub.PRRuntimeException: Error: You lack access required to execute RULE-OBJ-ACTIVITY RULE-OBJ-REPORT-DEFINITION PXRETRIEVEREPORTDATA #20140127T063059.806 GMT.


Steps to Reproduce



1. Receive the Input XML via JMS Queue.
2. Parse XML and create case.


Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules.
While using a service package that doesn't require authentication, there was a problem with calling activities with "require authentication" enabled from the service activity.


Resolution



This issue is resolved in Maintenance Level (ML) release 7.1.6.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

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