Support Article
Method "Page-Clear-Messages/Activity-End" class not recognized
SA-74871
Summary
The user has configured 12 nodes on a cluster. A long running query on a node (the 12th node) locked the database. The 'Class not recognized' error displays on the screen when the server is restarted. This occurs intermittently.
Error Messages
** Method "Page-Clear-Messages" (class "com.pega.pegarules.exec.internal.rules.methods.MethodPageClearMessages") is not recognized
</PrimaryPageContent><ParameterPageName>=unnamed=</ParameterPageName><ParameterPageContent><pagedata><CustomerAccountListPpxResults2colWidthCache2></CustomerAccountListPpxResults2colWidthCache2><PreActivitiesList><pagedata></pagedata></PreActivitiesList><CustomerAccountListPpxResults2colWidthCache1></CustomerAccountListPpxResults2colWidthCache1><pzHarnessID>HID34EB4B3ADB3DA9926BF952FDEBED58E4</pzHarnessID><CustomerAccountListPpxResults2colWidthCache4></CustomerAccountListPpxResults2colWidthCache4><CustomerAccountListPpxResults2colWidthCache3></CustomerAccountListPpxResults2colWidthCache3><EXPANDEDSubSectionObtainCustomerDataBBB>true</EXPANDEDSubSectionObtainCustomerDataBBB><EXPANDEDFlowActionSelectAccountB></EXPANDEDFlowActionSelectAccountB><RenderSingle></RenderSingle><ActivityParams></ActivityParams><inStandardsMode>false</inStandardsMode><EXPANDEDFlowActionCommissionInformationBB></EXPANDEDFlowActionCommissionInformationBB><pzTransactionId>7acdf6a23094221afa7924a94a15f320</pzTransactionId><EXPANDEDSubSectionObtainCustomerDataBBBB>true</EXPANDEDSubSectionObtainCustomerDataBBBB><EXPANDEDSubSectionCustomerGeneralInfoB>true</EXPANDEDSubSectionCustomerGeneralInfoB><bClientValidation>true</bClientValidation><StreamClass>Rule-HTML-Section</StreamClass><PreActivity>ValidateDelegateBranch</PreActivity><pzFromFrame>pyWorkPage</pzFromFrame><pzKeepPageMessages>false</pzKeepPageMessages><EXPANDEDFlowActionObtainCustomerDataBB></EXPANDEDFlowActionObtainCustomerDataBB><StreamName>ObtainCustomerData</StreamName><newSectionID>GID_1551781190108</newSectionID><EXPANDEDSubSectionObtainCustomerDataBBBBB>true</EXPANDEDSubSectionObtainCustomerDataBBBBB><BaseReference></BaseReference><AJAXTrackID>1</AJAXTrackID><pyActivity>ReloadSection</pyActivity><reloadPage>pyWorkPage</reloadPage><CustomerAccountListPpxResults2colWidthGBR></CustomerAccountListPpxResults2colWidthGBR><HeaderButtonSectionName></HeaderButtonSectionName><CustomerAccountListPpxResults2colWidthGBL></CustomerAccountListPpxResults2colWidthGBL><EXPANDEDFlowActionObtainCustomerDataB></EXPANDEDFlowActionObtainCustomerDataB><pzPrimaryPageName>pyWorkPage</pzPrimaryPageName><SectionIDList>GID_1551781221931:</SectionIDList></pagedata></ParameterPageContent></TraceEvent><TraceEvent sequence="3087" ruleNumber="" stepMethod="" stepPage="" step="" stepStatus="" eventType="DB Cache" elapsed="0" name="" ><Sequence>3087</Sequence><DateTime>20190305T102032.158 GMT</DateTime><EventType>DB Cache</EventType><EventName>Cache Hit (not found)</EventName><Interaction>138</Interaction><ThreadName>BRM/$TABTHREAD2</ThreadName><WorkPool>ACME-CorpBank-LoG-Work</WorkPool><ActivePALStat>pxRuleIOElapsed</ActivePALStat><Elapsed>0</Elapsed><FirstInput>Activity=ReloadSection</FirstInput><LastStep>ACME-FW-LOGFW-WORK-LOG VALIDATEDELEGATEBRANCH #20171016T075020.914 GMT Step: 1 Circum: 0</LastStep><DBTHighLevelOpID>209</DBTHighLevelOpID><DBTHighLevelOp>open instance of class Rule-Message by keys</DBTHighLevelOp><DBTNote>Looking for instance Rule-Message @BASECLASS!METHOD "PAGE-CLEAR-MESSAGES" (CLASS "COM.PEGA.PEGARULES.EXEC.INTERNAL.RULES.METHODS.METHODPAGECLEARMESSAGES") IS NOT RECOGNIZED in the Rule Resolution cache</DBTNote><DBTObjectClass>Rule-Message</DBTObjectClass></TraceEvent><TraceEvent sequence="3088" ruleNumber="" stepMethod="" stepPage="" step="" stepStatus="" eventType="DB Cache" elapsed="0" name="" ><Sequence>3088</Sequence><DateTime>20190305T102032.161 GMT</DateTime><EventType>DB Cache</EventType><EventName>Cache Hit (not found)</EventName><Interaction>138</Interaction><ThreadName>BRM/$TABTHREAD2</ThreadName><WorkPool>ACME-CorpBank-LoG-Work</WorkPool><ActivePALStat>pxRuleIOElapsed</ActivePALStat><Elapsed>0</Elapsed><FirstInput>Activity=ReloadSection</FirstInput><LastStep>ACME-FW-LOGFW-WORK-LOG VALIDATEDELEGATEBRANCH #20171016T075020.914 GMT Step: 1 Circum: 0</LastStep><DBTHighLevelOpID>210</DBTHighLevelOpID><DBTHighLevelOp>open instance of class Rule-Message by keys</DBTHighLevelOp><DBTNote>Looking for instance Rule-Message @BASECLASS!METHOD "PAGE-CLEAR-MESSAGES" (CLASS "COM.PEGA.PEGARULES.EXEC.INTERNAL.RULES.METHODS.METHODPAGECLEARMESSAGES") IS NOT RECOGNIZED in the Rule Resolution cache</DBTNote><DBTObjectClass>Rule-Message</DBTObjectClass></TraceEvent><TraceEvent sequence="3089" ruleNumber="45" stepMethod="Page-Clear-Messages" stepPage="" step="1" stepStatus="FAIL" eventType="Step End" elapsed="2" name="RULE-OBJ-ACTIVITY ACME-FW-LOGFW-WORK-LOG VALIDATEDELEGATEBRANCH #20171016T075020.914 GMT" inskey="RULE-OBJ-ACTIVITY ACME-FW-LOGFW-WORK-LOG VALIDATEDELEGATEBRANCH #20171016T075020.914 GMT" keyname="ACME-FW-LoGFW-Work-LoG ValidateDelegateBranch" rsname="LoGFW" rsvers="01-03-44" ><Sequence>3089</Sequence><DateTime>20190305T102032.158 GMT</DateTime><EventType>Step End</EventType><EventName>Step End</EventName><Interaction>138</Interaction><ThreadName>BRM/$TABTHREAD2</ThreadName><WorkPool>ACME-CorpBank-LoG-Work</WorkPool><Elapsed>2</Elapsed><FirstInput>Activity=ReloadSection</FirstInput><LastStep>ACME-FW-LOGFW-WORK-LOG VALIDATEDELEGATEBRANCH #20171016T075020.914 GMT Step: 1 Circum: 0</LastStep><ActivityNumber>45</ActivityNumber><EventKey>RULE-OBJ-ACTIVITY ACME-FW-LOGFW-WORK-LOG VALIDATEDELEGATEBRANCH #20171016T075020.914 GMT</EventKey><StepMethod>Page-Clear-Messages</StepMethod><ActivityName>VALIDATEDELEGATEBRANCH</ActivityName><StepNumber>1</StepNumber><mStepStatus>FAIL</mStepStatus><mStepStatusInfo>** Method "Page-Clear-Messages" (class "com.pega.pegarules.exec.internal.rules.methods.MethodPageClearMessages") is not recognized</mStepStatusInfo><PrimaryPageName>pyWorkPage</PrimaryPageName><PrimaryPageClass>ACME-CorpBank-LoG-Work-LoG</PrimaryPageClass><PrimaryPageContent>
Steps to Reproduce
Restart the server.
Root Cause
A defect or configuration issue in the operating environment
The SQL query that caused the database crash appeared when the agents were being executed. This Exception occurred when the network connection was lost between the JDBC pool and the database (due to firewalls closing idle the connections or time outs). This rendered the failing connection(s) in the JDBC pool, stale.
When a connection was lost with the database, then the agent's next run time could become a past time. Therefore, the agent did not run even when the database connection was restored or started manually through the System Management Application (SMA).
Resolution
Perform the following local-change:
Clear the Virtual Rule Cache instances of the Validation activity.
Published October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.