Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Rintu Julian (RJ000043)
Commonwealth Bank of Australia
Software Engineer
Commonwealth Bank of Australia
AU
RJ000043 Member since 2015 11 posts
Commonwealth Bank of Australia
Posted: May 20, 2016
Last activity: May 31, 2016
Posted: 20 May 2016 1:23 EDT
Last activity: 31 May 2016 9:29 EDT
Closed
Solved

Email Listener Issue


Hi,

Email listener in my application is getting moved to Sleeping mode for around 498905/ 468905 seconds when it encounters a situation of not being able to acquire lock on Inbox it is listening to. Listener is running on multiple nodes and sometimes it is in sleeping mode for hours on all nodes simultaneously. Can anyone please suggest a solution for this? Pega version in 7.1.7 and the latency period is set as 100 seconds.

Below is the debug info captured in Pega logs:

2016-05-19 17:35:49,076 [fault (self-tuning)'] [          ] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Service Package: EmailDefault

2016-05-19 17:35:49,076 [fault (self-tuning)'] [          ] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Service Class: Email-Email1-Sample-Work-External-InboundEmail

2016-05-19 17:35:49,076 [fault (self-tuning)'] [          ] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Folder: INBOX

Show More


Hi,

Email listener in my application is getting moved to Sleeping mode for around 498905/ 468905 seconds when it encounters a situation of not being able to acquire lock on Inbox it is listening to. Listener is running on multiple nodes and sometimes it is in sleeping mode for hours on all nodes simultaneously. Can anyone please suggest a solution for this? Pega version in 7.1.7 and the latency period is set as 100 seconds.

Below is the debug info captured in Pega logs:

2016-05-19 17:35:49,076 [fault (self-tuning)'] [          ] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Service Package: EmailDefault

2016-05-19 17:35:49,076 [fault (self-tuning)'] [          ] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Service Class: Email-Email1-Sample-Work-External-InboundEmail

2016-05-19 17:35:49,076 [fault (self-tuning)'] [          ] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Folder: INBOX

2016-05-19 17:35:49,076 [fault (self-tuning)'] [          ] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Latency: 100

2016-05-19 17:35:49,076 [fault (self-tuning)'] [          ] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Max. # of messages: 999

2016-05-19 17:35:49,076 [fault (self-tuning)'] [          ] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Max. processing time (seconds): 0

2016-05-19 17:35:49,076 [fault (self-tuning)'] [          ] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Host: imap.xx.xx.com, mPort: xxx, mProtocol: imap

2016-05-19 17:35:49,101 [fault (self-tuning)'] [  STANDARD] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Establishing new requestor.A3BCF6BBFAF9D3858FA173FD37DA9CEA6

2016-05-19 17:35:49,110 [fault (self-tuning)'] [  STANDARD] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - attempt to lock AppMailServer.INBOX : false

2016-05-19 17:35:49,132 [fault (self-tuning)'] [  STANDARD] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - We do not have lock on inbox

2016-05-19 17:35:49,132 [fault (self-tuning)'] [  STANDARD] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Will sleep for 468905 seconds

2016-05-19 17:35:49,132 [fault (self-tuning)'] [  STANDARD] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Cleanup lock requestor.

2016-05-19 17:35:49,132 [fault (self-tuning)'] [  STANDARD] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - delete requestor A3BCF6BBFAF9D3858FA173FD37DA9CEA6

2016-05-19 17:35:49,134 [fault (self-tuning)'] [  STANDARD] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Cleanup work requestor.

2016-05-19 17:35:49,134 [fault (self-tuning)'] [  STANDARD] [                    ] [                    ] (  services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Requestor id is null, no cleanup required.

Message was edited by: Lochan to add Category

Message was edited by: Lochan to add Category


Show Less
To see attachments, please log in.
Data Integration

Accepted Solution

Posted: 8 years ago
Posted: 31 May 2016 9:29 EDT
DurgadaVijayakumar (LochanaDurgadavijayakumar)

As result of investigation, the resolution is to apply HFix-23705

Please raise an SR with Pega GCS with the Request Type as Existing HotFix if you have a same issue!

Regards,

Lochan  |  Online Community Moderator  |  Pegasystems Inc.

To see attachments, please log in.
Posted: 8 years ago
Posted: 20 May 2016 1:54 EDT
Ajit Kumar (AjitKumar17)
PEGA
Technical Solutions Engineer
Pegasystems Inc.
IN

Hello Rintu,

Could you please check the applicability of the below articles for your use-case.

https://community.pega.com/support/support-articles/email-listener-stops-processing-emails-after-network-error

https://community.pega.com/node/163216

If you find the first article to be relevant, then I believe you might have to raise an SR or you may contact GCS to verify if we have any similar HFIX for PRPC 7.1.7.

Thanks!!

To see attachments, please log in.
Posted: 8 years ago
Updated: 8 years ago
Posted: 20 May 2016 15:50 EDT
Updated: 20 May 2016 15:52 EDT
Jeff Houle (HOULJ) Senior Software Engineer
Pegasystems Inc.
US

HFix-20069, mentioned in the first article, was ported to Pega 7.1.7 for another customer experiencing these issues in Pega 7.1.7.

Customers experiencing this problem should try to install HFix-23705 if possible.

To see attachments, please log in.
Posted: 8 years ago
Posted: 20 May 2016 14:38 EDT
Veera Gangababu Gollapalli (Gangababu)
PEGA
Principal Technical Solutions Engineer
PEG
IN

I could see Maximum processing time set to 0 secs.

2016-05-19 17:35:49,076 [fault (self-tuning)'] [ ] [ ] [ ] ( services.email.EmailListener) DEBUG EMAIL.AppEmailListener.AppMailServer [email protected] - Max. processing time (seconds): 0

I think Maximum processing time set to some positive value other than zero.

  • Maximum processing time - Enter the maximum duration in seconds for which this listener can process messages before the system forces it to start a rest period. The minimum is 1 second.

Are you seeing the issue every time or is there any specific pattern?

To see attachments, please log in.
Posted: 8 years ago
Posted: 22 May 2016 22:08 EDT
Rintu Julian (RJ000043)
Commonwealth Bank of Australia
Software Engineer
Commonwealth Bank of Australia
AU

Hi Gangababu,

I can confirm that Maximum processing time is set as 500 secs in Email listener rule. Not sure why it has been captured as 0 in Pegalog.

To see attachments, please log in.
Posted: 8 years ago
Posted: 21 May 2016 22:51 EDT
Ravikiran C (cr001)
Pegasystems Inc.
Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi Rintu,

Also Confirm us the PRPC version you are using.

Regards,

Ravi

To see attachments, please log in.
Posted: 8 years ago
Posted: 23 May 2016 10:31 EDT
Loving (NicholasLoving)

Hi Rintu,

I agree with Jeff Houle, this sounds like the issue Hfix-23705 was created to address. Please submit a Support Request describing the issue and request the hotfix (and reference this mesh post). The moderators will likely also want you to update this post with the SR number.

To see attachments, please log in.
Posted: 8 years ago
Posted: 24 May 2016 4:44 EDT
DurgadaVijayakumar (LochanaDurgadavijayakumar)

Hi Rintu,

Thank you for updating it here! I have tagged the SR number to your post above. You should be able to view it under Related Work column above!

Regards,

Lochan  |  Online Community Moderator  |  Pegasystems Inc.

To see attachments, please log in.

Accepted Solution

Posted: 8 years ago
Posted: 31 May 2016 9:29 EDT
DurgadaVijayakumar (LochanaDurgadavijayakumar)

As result of investigation, the resolution is to apply HFix-23705

Please raise an SR with Pega GCS with the Request Type as Existing HotFix if you have a same issue!

Regards,

Lochan  |  Online Community Moderator  |  Pegasystems Inc.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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