Question

2
Replies
27
Views
PradeepPydi Member since 2017 204 posts
Anthem
Posted: 5 months ago
Last activity: 5 months 1 week ago

PEGA0026 - PegaRULES PassivationDaemon Related.

Hi Team,

Could you please help understand the below mentioned exception (Related to passivation Daemon) root cause and resolution. 2020-04-14 19:39:12,819 GMT*8*PEGA0026*524*200*va22pwppeg303_csx2l*NA*NA*HCTX6G1E2GWJU6QMEILTXVHH12JASD8VR*MCDNCL466*Antm-FW-CSFW-Work*null*d088f624a6f1fbf2bc5c224351777e95*N*124*HCTX6G1E2GWJU6QMEILTXVHH12JASD8VR*5412*PegaRULES PassivationDaemon*TABTHREAD1*com.pega.pegarules.data.internal.store.AlertHelper*NA*Activity=ReloadSection*Rule-Obj-Activity:ReloadSection*@BASECLASS RELOADSECTION #20170710T071709.574 GMT Step: 10 Circum: 0*42*****pxRunOtherRuleCount=1;pxInteractions=1;pxLegacyRuleAPIUsedCount=1;pxRunStreamCount=3;pxInputBytes=2,124;pxTotalReqCPU=0.02;pxRunModelCount=6;pxOutputBytes=41,253;pxRulesUsed=160;pxRunWhenCount=29;pxRulesExecuted=53;pxOtherCount=1;pxTrackedPropertyChangesCount=9;pxTotalReqTime=0.02;pxActivityCount=6;pxAlertCount=1;pxOtherFromCacheCount=4;*NA*NA*NA*NA*NA*NA*Time to acquire a connection has exceeded the alert threshold of 100 ms: 524 ms. DBName [pegadata] Initial [False] Connection [4] Status [New] Type [JNDI Name Common] Conn Mgr [App Server] Activate Time [0] DBInfoMap Time [0] Connection Count [5]*  

Pega Platform 7.3.1 Low-Code App Development Performance Healthcare and Life Sciences
Share this page LinkedIn