Support Article

Too many alerts in logs while creating cases in batch

SA-33292

Summary



User is using a custom soap service to create cases in Pega. During the creation process it is invoking a datapage D_Instuctions, which is from strategic app using a report definition which in turn retrieves the data from a data table in Sample database table.

During this, user is getting too many alerts in the alert log file, as they are creating cases in batch.


Error Messages



2017-01-17 18:06:05,648 GMT*8*PEGA0026*111688*100*2fb2622ca50e8e29280f281c19dda0c1*NA*NA*A703D17EAB0A0D4C4092940A3DFB26955*WF_TEST*NAV-FW-NavWrntyFW-Work*NavWrntyFW:01.01.10*b54805032ed3f30431cf13caea17eb98*N*1*A703D17EAB0A0D4C4092940A3DFB26955*1636*WorkManager.PegaWorkManager : 9*STANDARD*com.pega.pegarules.data.internal.access.ConnectionManagerImpl**NAV-FW-NavWrntyFW-Work-WR-CL-ClaimFile.CreateClaimsSkipDuplicates*Rule-Obj-Activity:CreateClaimsSkipDuplicates*RULE-OBJ-REPORT-DEFINITION PXRETRIEVEREPORTDATA #20150624T081340.776 GMT Step: 30 Circum: 0pxRDBIOCount=11;pxDBOutputBytes=45,456;pxLegacyRuleAPIUsedCount=18;pxDeclarativeRulesInvokedElapsed=0.14;pxRunOtherRuleCount=15;pxOtherCount=6;pxInteractions=1;pxRuleCount=55;pxOtherIOElapsed=0.98;pxTotalReqTime=517.09;pxRunWhenCount=165;pxRuleIOElapsed=0.00;pxDeclarativeRulesInvokedCount=455;pxActivityCount=379;pxFlowCount=24;pxRDBRowWithoutStreamCount=2;pxDeclExprCtxSensUseCount=47;pxOtherIOCount=17;pxRDBWithStreamCount=1;pxTrackedPropertyChangesCount=530;pxTotalReqCPU=0.20;pxDBInputBytes=61,684;pxRunModelCount=50;pxRulesUsed=3,013;pxRDBIOElapsed=514.54;pxRDBWithoutStreamCount=2;pxDeclExprCtxFreeUseCount=242;pxRDBRowWithStreamCount=1;pxAlertCount=7;pxRuleFromCacheCount=55;pxRulesExecuted=1,148;pxOtherFromCacheCount=53;*Embed-ReportContent*NA*Embed-ReportContent*NA*ReportingPegaMfg-Int-InstructionMappingInstructionStepsListReport;doActivity Rule-Obj-Report-Definition;Java;RULE-OBJ-ACTIVITY RULE-OBJ-REPORT-DEFINITION PXRETRIEVEREPORTDATA #20150624T081340.776 GMT Step: 30 Circum: 0;doActivity Rule-Obj-Activity:pxRetrieveReportData;165 additional frames in stack;*pyPageName=pyDataSource1484676253950;pyDefinitionKey=RULE-DECLARE-PAGES D_INSTRUCTIONS #20151204T063057.290 GMT;CopyAlways=true;pyExecuteOnDataPage=false;pySavedInPegaVersion=7.1.9;pyReportName=InstructionStepsListReport;pyReportParamPageName=pyReportParamPage;pyResDataTransform=MapInstructionSteps;pyPassCurrentParamPageForRespDT=;pyForEachCount=2;retainUnusedJoins=;ItemID=999999;pySkipSummaryProcessing=;pyClassName=PegaMfg-Data-Instruction;Type=RETURNINS;pyReportClass=PegaMfg-Int-InstructionMapping;pyPageStructure=list;pyRunType=FullResolve;pyRuleSet=PegaManufacturing;*Time to acquire a connection has exceeded the alert threshold of 100 ms: 111688 ms. DBName [sample] Initial [False] Connection [20] Status [New] Type [JNDI Name Common] Conn Mgr [App Server] Activate Time [111688] DBInfoMap Time [0] Connection Count [19]*


Steps to Reproduce

  1. Create a Soap service to create cases in Pega.
  2. Invoke the service.
  3. Check the alert log file.


Root Cause



The Set instruction data transform is having D_instruction data page which has a reference of report definition, which in turn is defined in the sample database and that was triggering the issue which was referenced in users activity.

Resolution



Perform the following local-change step:

Remove the set instruction data transform from activity or comment out the code in the data transform to avoid the calling of the D_Instruction data page.

Published February 3, 2017 - Updated February 15, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.