Close popover
Harish Gunneri (Harish_GCS)
Senior Software Solutions Engineer
Pegasystems Inc.
Harish_GCS Member since 2014 6 posts
Posted: May 3, 2016
Last activity: May 17, 2016

Email Listener poor performance on Pega 7.1.7 - Need design recommendations

Hi All,

Posting this on behalf of client as they need some design recommendations to improve the EmailListener performance.

Have 1 Email Listener instance running on one node to process incoming email messages, the listener service activity does the following as soon as an email gets picked up.

Create a new work object, Create PDF from email content,  Attach PDF, and call some external REST service to upload document content. These are the whole bunch of operations which runs on EmailListener thread for a single email. This usually takes 2-3 mins to finish the job depends on the size of the email content.

On an average, this listener has to process 200-250 emails per day and have the below configurations set on Email Listener.


With the provided details on the load, processing time, configuration -

1. User would like to know if there are any recommendations to improve the listener performance? (like increasing concurrent threads or have another listener thread instance?)

2. User requires an API to check the listener status and the last execution date time for monitoring? (suggested to use AES or write a custom java to access the MBean)

Any observations/suggestions would be a great help.

Data Integration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.