Increase Stream Response size threshold using DSS
Admin wants to increase stream response size threshold to 400 KB and has added below parameter in dynamic system setting. The change isn't taking effect andPega Alert is still using 200 KB threshold.
Paramater Name: prconfig/alerts/clientbytesreturned/threshold/default
Value : 409600
no error message
Steps to Reproduce
Set a dynamic system setting.
The root cause of this problem is defect/misconfiguration in the PRPC operating environment. In the prconfig.xml file that is being used on this system we see this:
<env name="initialization/settingsource" value="file" />
<env name="alerts/clientbytesreturned/threshold" value="204800" />
With the settingsource set to "file" that indicates that the settings in the file are what are used. If the setting source is "merged" then the settings in the file will be merged with the dynamic system settings. If a setting is specified in both the prconfig and in a Dynamic System Setting then the file will take precedence. This explains why the DSS is not getting picked up.
This issue is resolved by making the following change to the PRPC operating environment:
To use a DSS you will need to update the prconfig.xml file to set the setting size to "merged" and remove the alert threshold you are trying to set:
<env name="initialization/settingsource" value="merged" />
To use prconfig to set this threshold update prconfig.xml with the appropriate value:
<env name="alerts/clientbytesreturned/threshold" value="409600" />
When making a change to prconfig.xml with an ear deployment you need to either externalize the prconfig.xml file or you need to update the file in the prresouces.jar and then add the updated jar file to your ear. Then you will need to undeploy the existing ear file and redeploy the updated ear.
0% found this useful