Posted: 3 Aug 2017 6:39 EDT Last activity: 4 Aug 2017 9:09 EDT
SLA Agent is behaving separately on different nodes
Hello All, We are facing issue and not able to trace it out. SLA Agent is configured on two nodes, on one node it is running on correct time but in one node it is updating SLA with 3 hour delay. Can any one suggest reason behind this? Hope you are able to understand my query. We are using pega 6.2 SP1. Cheers.. Shivam Garg
***Edited by Moderator, Maryrita: moved to Product Support from Applications***
***Edited by Moderator Marissa to update categories***
I'm not sure I've understood what you mean here by 2 nodes.
To Qualify; Normally if the SLA Agent is running I'd expect that it issue a query against the PR_SYS_QUEUE_SLA table based on what entries have a pyMinimumDateTimeForProcessing that is older than the current time.
So if you have one node which is tardy by 3 hours, then would the other node handle all of the SLA entries and the node which runs 3 hours late would simply not find any records?
But by 2 nodes, I'd assume this to mean 2 application servers nodes pointing to 1 database instance.
Here, by 2 nodes, do you mean 2 application server nodes point to 2 database instances?
Or do you mean that the SLA agent (on the problem node) is correctly processing the activity associated with the SLA goal. But when it creates the new row in PR_SYS_QUEUE_SLA for the DEADLINE, that this is incorrectly calculating the pyMinimumDateTimeForProcessing for that row?
OK. So how have you established that the 3 hour delays related to a particular node?
Do you see the actions running late only on the one node? Or is it possibly that it's actually running later on both nodes, but approximate 50% of the time on each?
If it's definitely specific to a node; Do if you go to SMA for both nodes and examine the contents of Administration > Configuration Management do you see any differences which may account for the time delay?