Too much of PEGA0104 alert in production
A lot of PEGA0104 alert is being observed in the production server. What could be the possible reason for this and how it can be resolved?
2020-01-23 06:13:56,581 GMT*8*PEGA0104*819549*120000*4002dea79ba02e1a9d2ad917aa7ccc73*NA*NA*BJ91K7H48025G33OK7CYUKN3TMWZQZYG6A*NA*PegaSample*null*6431a92eb843dd43193d0f3ad85a95bb*N*682*BJ91K7H48025G33OK7CYUKN3TMWZQZYG6A*1321*PegaRULES ManagementDaemon*STANDARD*com.pega.pegarules.session.internal.async.LongWaitingBatchTasksAlertGenerator*NA*(ManagementDaemon)*NA*NA*NA*****NA*NA*NA*NA*NA*NA*NA*Long waiting background tasks detected. Number of waiting tasks: 33; Waiting time of the oldest task : 819 seconds*
I have already gone through THIS article.
PRPC 8.1.4
Accepted Solution
Updated: 2 Sep 2020 10:59 EDT
LTIMindtree
IN
Hello Piyush,
We are also facing this PEGA0104 issue, after we have upgraded our environment from 7.2.2 to 8.2.3.
Please find the reply from the SR we had raised This may be useful.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
In Pega 8 , We have removed SMA and introduced Admin studio . There are lot of backed jobs running for this. SO it require more threads to run this backed activities. We already check with our SMA . It is not sufficient with the default threadpool size , Because of this we are observing lot of Pega0104 alert. As suggested please increase the thread pool size with the below prconfig setup . <env name="agent/threadpoolsize" value="XX"/>
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
After we had raised our threadpool size to 50 from default value, we didn't see any PEGA0104 alert.
Kindly share us , if there is any issue you are facing due to this PEGA0104 alert. i.e Impact or change you observed after this alert .
Thanks,
S.Seetharaman
Accepted Solution
Updated: 2 Sep 2020 10:59 EDT
LTIMindtree
IN
Hello Piyush,
We are also facing this PEGA0104 issue, after we have upgraded our environment from 7.2.2 to 8.2.3.
Please find the reply from the SR we had raised This may be useful.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
In Pega 8 , We have removed SMA and introduced Admin studio . There are lot of backed jobs running for this. SO it require more threads to run this backed activities. We already check with our SMA . It is not sufficient with the default threadpool size , Because of this we are observing lot of Pega0104 alert. As suggested please increase the thread pool size with the below prconfig setup . <env name="agent/threadpoolsize" value="XX"/>
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
After we had raised our threadpool size to 50 from default value, we didn't see any PEGA0104 alert.
Kindly share us , if there is any issue you are facing due to this PEGA0104 alert. i.e Impact or change you observed after this alert .
Thanks,
S.Seetharaman