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

Email Listener startup fails during JVM start

SA-66311

Summary



On starting the Pega application server, the EmailListener fails to start and an error message displays.
After the system starts, the EmailListener is started manually.



Error Messages



- Only authenticated client may start this activity: RULE-OBJ-ACTIVITY HO GETPKCS7FROMAWS #20180913T095803.775 GMT ReqID=A1SVEULZAMOROE4J3HNT5ZP5EF3NBI0EM


Steps to Reproduce

  1. Use Global Resource Syntax (GRS) for several configuration parameters of an EmailListener and the related EmailAccount.
  2. Reference the source data page through the GRS. The data page is populated through several activities that require authentication.


Root Cause



An EmailListener is not a requestor. Therefore, it does not have an identity and is not authenticated. The requestor login provided with the configuration is only used for the Service Activity that processes emails. The login is not for the email listener.
While the access to a data page through GRS does not require authentication, the activities to populate the data page may require authentication. However, when called in the context of the EmailListener startup, there is no authentication context. Hence, the error message occurs.



Resolution



Perform the following local-change:

Populate the GRS data page through an activity that does not require authentication.


 

Published October 17, 2018 - 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