Question7Replies3528Views Brahmesh@ Member since 2013 145 posts Capgemini Posted: 4 years agoLast activity: 4 years 3 months ago Closed Stream Response Size (PEGA0029)Getting below critical alert in alert log file.Stream exceeded client response byte threshold (pxObjClass=Rule-Obj-XML;pyStreamName=GetObjectDecryptedBody;pyXMLType=MapFrom;).PAL Data :pxRDBIOElapsed=0.00;pxConnectElapsed=0.35;pxInteractions=1;pxRuleCount=5;pxRDBIOCount=1;pxRunStreamCount=1;pxInputBytes=172;pxTotalReqCPU=0.10;pxRunModelCount=4;pxConnectCount=1;pxRulesUsed=137;pxRunWhenCount=3;pxRulesExecuted=15;pxOtherCount=5;pxRuleFromCacheCount=5;pxOtherIOElapsed=0.00;xTrackedPropertyChangesCount=4;pxDBInputBytes=2,990;pxTotalReqTime=0.37;pxActivityCount=9;pxOtherIOCount=1;pxAlertCount=1;pxOtherFromCacheCount=9;Alert is generating while system is reading the attachment from external system by making the web service call.Seems ,if attachment size > 200 KB then alert is being generated from response XML steam rule . Please correct me if understand is wrong.To avoid this alert , we are planning to update the following environment variable.prconfig/alerts/clientbytesreturned/threshold/default 204800 ----Default .Is it suggestible to update variable ? Please let me know if we any consequence by increasing threshold value to 10 MB. System Administration Data Integration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 4 years agoGangababu PEGA replied to Brahmesh@By increasing the threshold timeout , you couldn't see the alert in PegaAlert log until it exceeds beyond updated threshold level.You should verify why it is taking time when attaching 200kb file. Posted: 4 years agoKevinZheng_GCS PEGA replied to GangababuI concur, here are some of the suggestions you can try: https://pdn.pega.com/sites/pdn.pega.com/files/help_v719/procomhelpmain… Posted: 4 years agoBrahmesh@ Capgemini replied to KevinZheng_GCSHi Kevin,I already gone through above help page,It's not occurred from UI rules . it's coming up during map the response from external system (service). Posted: 4 years agoBrahmesh@ Capgemini replied to KevinZheng_GCSMy concern over here is ,Do we have any implications if below Env. variable is increased to 10 MB .prconfig/alerts/clientbytesreturned/threshold/default 204800 Posted: 4 years agoKevinZheng_GCS PEGA replied to Brahmesh@no, it is not going to change your system behavior except it does not logout alerts into alert logs. Posted: 4 years agoBrahmesh@ Capgemini replied to KevinZheng_GCSok.. we are good if this alert is not logged in alert logs by doing prconfig change. Posted: 4 years agoBrahmesh@ Capgemini replied to GangababuThis is nothing related to timeout ,and it's all about size of HTML stream .prconfig/alerts/clientbytesreturned/threshold/default 204800 ( Bytes =200KB).