Question
Bank Of America Continuum India
IN
Last activity: 26 Nov 2018 10:55 EST
What is the default behavior of Pega OOTB Agents/Application specific agents and JMS queues when server/node of Environment goes down.
I would need help in understanding the default behavior of agents and listeners when the server/node goes down due to some issue or system crashes. Below are few scenarios.
If a agent is processing any queued item, will it get moved to broken queue and will have to be re-queued manually or it will not complete and will get processed when the server comes back online.
If a JMS listener is processing the item in its respective queue, will the processing fail to complete or it will throw a error/exception due to this and will be processed at a later time.
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
IN
When server goes down abruptly, the queue item which is being processed by standard agent will remain in now-processing state and on server start up the queue item will not be picked . So the item remains in now-processing state. As part of SR-A76163, hot-fix was given to handle this use case . When server comes up next time queue items in now-processing state are moved to scheduled state so that next agent run picks the items.
Bank Of America Continuum India
IN
Thanks Lokas. Can you please provide the hotfix number related to SR-A76163. I was not able to find the SR details.
Thanks again!!!
Bank Of America Continuum India
IN
Thanks. One last question- Do we need to have this hotfix installed in order to achieve this default behavior or Pega base setup package already have this functionality in place.
Pegasystems Inc.
IN
Do let us know the SR# when you create one, we will connect the SR# to the post for the benefit of support engineer working on the issue.
Thanks!