SA-9278

Summary

The customers project has been in production for over a year and currently there have been upto 85% of all alerts linked to Pega0004 for SystemWorkIndexer.

Error Messages

2015-03-23 23:00:39,083 GMT 6 PEGA0004 51728552 50000000 7b1aa4e6522db9ebd7270610c6015e21 B9CEDD27954E1F9475D9844F572CDFE24 System PegaSample PegaRULES:06.02 5c89200298f259493e14772fd3b7ba22 N 1 7138 [ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)' STANDARD com.pega.pegarules.data.internal.access.DatabaseImpl System-Work-Indexer.SystemWorkIndexer Rule-Obj-Activity:SystemWorkIndexer SYSTEM-WORK-INDEXER SYSTEMWORKINDEXER #20110712T001537.109 GMT Step: 1 Circum: 0 253:haveAccessWithFrame :System-Work-Indexer;254:haveAccessWithFrame :System-Work-Indexer;255:haveAccessWithFrame :System-Work-Indexer;256:haveAccessWithFrame :System-Work-Indexer;257:haveAccessWithFrame :System-Work-Indexer;258:haveAccessWithFrame :System-Work-Indexer;259:haveAccessWithFrame :System-Work-Indexer;260:haveAccessWithFrame :System-Work-Indexer;261:haveAccessWithFrame :System-Work-Indexer;262:haveAccessWithFrame :System-Work-Indexer;263:haveAccessWithFrame :System-Work-Indexer;264:haveAccessWithFrame :System-Work-Indexer;265:haveAccessWithFrame :System-Work-Indexer;266:haveAccessWithFrame :System-Work-Indexer;267:haveAccessWithFrame :System-Work-Indexer;268:haveAccessWithFrame :System-Work-Indexer;269:haveAccessWithFrame :System-Work-Indexer;270:haveAccessWithFrame :System-Work-Indexer;271:haveAccessWithFrame :System-Work-Indexer;272:haveAccessWithFrame :System-Work-Indexer;273:haveAccessWithFrame :System-Work-Indexer;274:haveAccessWithFrame :System-Work-Indexer;275:haveAccessWithFrame :System-Work-Indexer;276:haveAccessWithFrame :System-Work-Indexer;277:haveAccessWithFrame :System-Work-Indexer;278:haveAccessWithFrame :System-Work-Indexer;279:haveAccessWithFrame :System-Work-Indexer;280:haveAccessWithFrame :System-Work-Indexer;281:haveAccessWithFrame :System-Work-Indexer;282:haveAccessWithFrame :System-Work-Indexer;283:haveAccessWithFrame :System-Work-Indexer;284:haveAccessWithFrame :System-Work-Indexer;285:haveAccessWithFrame :System-Work-Indexer;286:haveAccessWithFrame :System-Work-Indexer;287:haveAccessWithFrame :System-Work-Indexer;288:haveAccessWithFrame :System-Work-Indexer;289:haveAccessWithFrame :System-Work-Indexer;290:haveAccessWithFrame :System-Work-Indexer;291:haveAccessWithFrame :System-Work-Indexer;292:haveAccessWithFrame :System-Work-Indexer;293:haveAccessWithFrame :System-Work-Indexer;294:haveAccessWithFrame :System-Work-Indexer;295:haveAccessWithFrame :System-Work-Indexer;296:haveAccessWithFrame :System-Work-Indexer;297:haveAccessWithFrame :System-Work-Indexer;298:haveAccessWithFrame :System-Work-Indexer;299:haveAccessWithFrame :System-Work-Indexer;300:haveAccessWithFrame :System-Work-Indexer;301:haveAccessWithFrame :System-Work-Indexer;302:haveAccessWithFrame :System-Work-Indexer; pxTotalReqTime=31.25;pxInteractions=1;pxJavaStepCount=1;pxAlertCount=1;pxRulesUsed=2;pxJavaStepElapsed=16.96;pxOtherIOElapsed=14.30;pxRulesExecuted=1;pxRDBWithStreamCount=300;pxDBInputBytes=51,728,552;pxOtherIOCount=467;pxRDBRowWithStreamCount=300;pxTotalReqCPU=7.35;pxOtherCount=167;pxActivityCount=1;pxConnectCount=601;pxConnectElapsed=9.53; NA NA NA NA Java;RULE-OBJ-ACTIVITY SYSTEM-WORK-INDEXER SYSTEMWORKINDEXER #20110712T001537.109 GMT Step: 1 Circum: 0;doActivity Rule-Obj-Activity:SystemWorkIndexer;initial Executable;0 additional frames in stack; QueueNumber=5;pzMaxRecords=0;LockString=5 System-Work-Indexer.SystemWorkIndexer System-Work-Indexer;pyQueueClass=System-Work-Indexer; The number of database bytes input for this interaction has exceeded the WARNING level for Requestor B9CEDD27954E1F9475D9844F572CDFE24, operator System Maximum bytes: 50000000 Actual bytes: 51728552

Steps to Reproduce

there are aproximately 10,000 live work objects.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. The reason for the high number of alerts is that the SystemWorkIndexer is reporting an uncompressed size which will hit the threshold more often hence producing the alerts more frequently. This was meant to be ignored like it is in the SystemIndexer.

Resolution

The reason for the alerts are because a line of code is missing in the SystemWorkIndexer to ignore Byte governer during the SystemWorkIndexer as it does for the SystemIndexer. This was verfied with the engineers who recommended adding a line into the activity similar to the one in the SystemIndexer shown in the image below. The error is likely to appear because at the time this activity is called it is reporting on uncompressed data hence the size is causing the alert.



Recommendation given to the customer was to add an extra line into the SystemWorkIndexer activity.