Pega 8.7.4 Next Run in Agent Schedule not updating after a week of Restart.

General
, ,
1

Hi

We have upgraded to Pega 8.7.4 last month. We have one background processing node where SenCorr of Pega-Procom agent runs. Its a Standard Periodic Agent. We see that the agent Next Run Time doesnt get updated after a week of restart and it stops at 1:00 AM EST. We have been observing this every week. Is there any setting we need to change? Once we restart our background processing node there is no issue exactly for a week.

Logs doesnt show anything?

I have seen similar posts below where Hotfix has been provided. Before raising INC wanted to check there for expert opinion.

Next Run in Agent Schedule not updating in Pega 7.1.8 | Pega?

Thanks

Arvind B

2

@Arvind

Did you get any resolution for your issue ? I am facing a similar situation in 8.7.3.

Regards,

Akash

3

@Arvind hi Arvind , We are facing similar issue in 8.7.2. You were able to fix this issue in your application?

4

@Arvind Please can you update PSC posts if you log support incidents? I see that you logged the following in May and it was resolved in June

INC-A685 (Pega 8.7.4 Next Run in Agent Schedule not updating after a week)

Solution description:

This issue is due to exhausting ThreadPool by ADMSNapshot agent.

This issue has been fixed in Pega 8.7.5. If you are not using Pega Marketing, please disable ADMSnaphot agent. Also we recommend to increase agent/threadpoolsize setting to 100 as a safety net and recommendation. In order to do that, please set below DSS:

Owning RuleSet Pega-Engine Setting Purpose prconfig/agent/threadpoolsize/default Value 100

You were requested to restart all nodes after setting the DSS above agent.