Pega Notification stops working and starts only upon server restart
Hi,
I added pxNotify in an activity and set Param.NotificationName and Param.RecipientsList as one of the operators who need the notification. (Not the current operator). This is working fine and I could get the bell icon displayed in top right of the port. But, this is getting stopped in a while and I could make it work once server restarted. All the old notifications also displayed once server restarted.
Could anyone help on finding the root cause of the issue as we cannot restart every time when notification are not working?
Mastek
GB
Evonsys
LK
@Bhavya Thanks for the response. As server was restarted already, I couldn't get the status at the time of issue. Currently it is in Normal status. I hope this will help me identify the issue next time.
Updated: 4 May 2022 0:31 EDT
Evonsys
LK
Notification stopped again and the stream nodes in Configure->Decisioning->Infrastructure->Stream shows as UNREACHABLE. Couldn't spot in logs as well. Any specific reason that causing this issue?
Mastek
GB
@Nirushiya In our case, the stream nodes need atleast 1Gb space to be free to keep running. Check the space in your tomcat , if thats valid for you.
Regards
Bhavya
Updated: 26 Apr 2022 0:12 EDT
Lventur
IN
Pega will be holding all notification and pulse related information in below mentioned tables..
pyProcessNotification this is the queue processor which is responsible for processing all notification and pulse related request.. Please check first queue processor is running without any issues and then trace queue processor and check whether you are getting any exceptions inside processor..
Note - Just make sure your queued notification request having entry in below mentioned tables..
Table Name
PegaSocial-Message,
Data-Notification-Parameters,
Data-Notification-Recipient,
Pega-Notification
Evonsys
LK
@Gunasekaran Baskaran , Thanks for the response. Queue process is running and it has many instances scheduled. but, not getting processed or in broken status. Analysed the tables and no entries made after the issue has occurred in two of the tables.
PegaSocial-Message - no data, Data-Notification-Parameters - no data, Data-Notification-Recipient - only the instances before the issue occurred, Pega-Notification - only the instances before the issue occurred.
Lventur
IN
Please check why in back-end needed tables entries are not getting added..
I am thinking that should be the problem, needed information is not avail for processor to process pulse request successfully...
@Nirushiya I think pega uses a queue processor in the backend to generate these notifications. We face this kind of issue, when the stream node goes down intermittently.
If it happens again, can you go to Configure->Decisioning->Infrastructure->Stream and check the status. If the status is "Normal" that you can rule this theory out. But if the stream node is down, then some more investigation would be needed at your end to find the root cause of it.
Regards
Bhavya