Support Article

Email Listener processing email request very slow

SA-25717

Summary




User has performed upgrade from PRPC 6.3 to Pega 7.1.9. They followed copy schema approach. User is facing performance issue with the Email Listener. It takes a large time to process a simple email.

Error Messages



Not Applicable

Steps to Reproduce



1. Perform upgrade from PRPC 6.3 to Pega 7.1.9.
2. Monitor the performance of the Email Listener processing.

Root Cause



In the Alert logs, there were numerous Pega0011 and Pega0005 ALERTS associated with the custom Email Listener.

Looking at the Pega0005 data, we identified that it was taking 3.5 minutes for processing a MERGE query. Assuming that each email that is processed is executing the merge query.

The CustomActivity was running Obj-Save and creating this MERGE query:

Obj-Save
RULE-OBJ-ACTIVITY WORK-PROCESSEMAIL CUSTOMACTIVITY #20160516T041527.463 GMT Step: 19 Circum: 0
doActivity Rule-Obj-Activity:CustomActivity
Call Work-ProcessEmail.CustomActivity
RULE-OBJ-ACTIVITY WORK- PYCREATEANDMANAGEWORKFROMEMAIL #20160518T051823.091 GMT Step: 12 Circum: 0 
2 additional frames in stack

 

Resolution



Reported behavior was caused by MERGE query for one of the external database table where it does not have Index for pzInsKey, instead they have primary key index on the ID column. 

User is suggested to involve their database administrator to review the performance issue originating due to the custom database table between 2016-07-16 07:11:41,919 GMT and 2016-07-16 08:24:15,573 GMT.

Create the missing index for pzInsKey for the particular table to resolve the issue.
 

Published July 16, 2016 - Updated August 18, 2016

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.