Question
MacQuarie Bank Ltd
AU
Last activity: 26 Nov 2021 0:53 EST
Pega 7.3.1 email listener not getting refreshed as per latency defined
Hi Team,
I am facing issue in email listener. It is working fine when i restart the listener services. But after restart it is working fine for 2mins and after that it is not working as per latency define in the listener.
Can you please help me.
Pega version is 7.3.1.
Server used is Jboss.
Environment is SIT
Nodes - 1
its a banking project so hiding the rule names in the screen shot.
Getting as last run time exceed the pooling interval time defined as 10sec.
No idea why it is not running ?
MacQuarie Bank Ltd
AU
***Edited by Moderator: Pooja Gadige to add capability tag*** what is this did not understand..
Updated: 23 Nov 2021 6:16 EST
Pegasystems Inc.
IN
Hello @MallikarjunA5355
The Pega Collaboration Centre's moderation team has added missing capability tag to the above post, which helps in increasing the chances of getting a reply to the post.
Thank you.
Pegasystems Inc.
IN
Hi @MallikarjunA5355 Could you please share snapshots of Listener properties under Email Listener rule and Pooling tab under Service Package to check few configuration settings. Thank you, Aditya
MacQuarie Bank Ltd
AU
@adityarao Hi team,
Thanks for your reply.
I observed that when i am running search reindex the listener is getting down.
When i cancelled the indexing the listener is working as expected.
Thank you,
Mallikarjun
Pegasystems Inc.
IN
Hi @MallikarjunA5355 Do we have background processing and search defined on same node? In that case, when re-indexing is performed it might be impacting the Listeners.
To continue our investigation, please raise a request in MSP portal and share Pega Rules and Alert logs for further debugging.
Thanks,
MacQuarie Bank Ltd
AU
@adityarao Hi Aditya,
Yes we have only one node in the SIT.
In that case, when re-indexing is performed it might be impacting the Listeners.--This is the issue i am facing.
Thanks,
Mallikarjun
Pegasystems Inc.
IN
Since Listeners run on Background Processing and, in this scenario, re-indexing is occupying the complete memory. We have two options to get this worked.
1) Define a new node for Background Processing and Search.
or
2) Wait until the re-indexing is completed and then start the Listeners.
Please let me know if this fixes the issue.
Thanks,