Question
JP Morgan Chase & Co.
US
Last activity: 16 Sep 2019 11:55 EDT
Pega 8.2.2 Admin studio showing email listeners errors count increasing through listener is working fine
We have 2 email listeners in our application. Each one is running on 2 nodes. We upgraded pega version from 7.2.1 to 8.2.2 2 days back and we are seeing email listener error counts increasing though the listeners are processing each and every email from their respective mailboxes successfully. In pegarules and alert logs, we can errors like "com.pega.platform.integrationcore.client.email.EmailClientException: Unable to connect email client due to : Connection reset"
"com.pega.platform.integrationcore.client.email.EmailClientException: Unable to connect email client due to : Connection reset"
Attached sample error stack. Can you please help us out in identifying this issue and from where does admin studio displays this error count (source table of these errors).
***Edited by Moderator: Lochan to update platform capability tags***
Pegasystems Inc.
US
if this is sporadic, can you check this link: https://community.pega.com/support/support-articles/email-listener-sporadically-fails-connection-reset-error
Pegasystems Inc.
IN
Please enable the debug on the below classes and share the logs:
com.pega.pegarules.integration.engine.internal.services.email.EmailListener
com.pega.pegarules.integration.engine.internal.services.email.EmailHelper
JP Morgan Chase & Co.
US
We don't have access to login to specific nodes in production. Email listeners are running on BackgroundProcessing nodes and via SSO, we can login only to user nodes. Unfortunately, from Admin Studio when we enable debug on these classes, it enables only on the node we have logged in. Is there a way to enable logger on a node without actually login into that node?
Another question, Errors count we see in Admin studio for listeners, are those the counts of alerts we have in pega alert file? Is there any source data table of these numbers?
Pegasystems Inc.
IN
Hi Sonal,
Please use the below path to enable logging in specific node:
Admin Studio > Resources > API
Go to Loggers in System Management and then set the logger in PUT :
Regards,
Vikash