( platform.message.CoreMessage) WARN - The message exceeds recommended size of :8000.
Hi,
Does anybody know why the above mentioned warning is generated in our PEGARules.log and how we might get rid of it?
We are running Pega 7.2.2 on Websphere 8.5
Kind regards,
Arjan Maus
***Updated by moderator: Lochan to update Categories***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
US
that works in prconfig. Alternatively, you can use DSS with the setting purpose like 'prconfig/messaging/core-message/message-size/default' with owning ruleset as 'Pega-Engine' - the DSS is preferred in general as it applies to all nodes within the pega cluster.
Pegasystems Inc.
US
This is the javadoc from the CoreMessage class:
CoreMessage is the implementation of the kernel level message api. It is just a warning regarding the message size, which is controlled by prconfig setting "messaging/core-message/message-size" with a default value of 8000 bytes.
Achmea
NL
Hi Kevin,
I'm a colleague of Arjan and I've checked our prconfig.xml and this line is not set, does it look like this?
<env name="messaging/core-message/message-size" value="8000"/>
Or is there a Dynamic system setting which is possibly better so we don't see this Warning anymore in the log?
Accepted Solution
Pegasystems Inc.
US
that works in prconfig. Alternatively, you can use DSS with the setting purpose like 'prconfig/messaging/core-message/message-size/default' with owning ruleset as 'Pega-Engine' - the DSS is preferred in general as it applies to all nodes within the pega cluster.
Infosys LTD
AU
Hi Kevin, if its just a warning can we increase the value till the warning goes away and what would be the impact if we increase to much higher limits.
May be explanation of what it actually does will help.
Thanks
Dalbir
Securities and Futures Commission
HK
Hi,
We encountered the exact same warning and I understand that it can be properly addressed by setting the configuration. But out of curiosity, what does this warning message actually implies? And is there any significant impact on the system?
Regards,
Raymond
Infosys LTD
AU
Hi Team,
Even we are getting same Warning despite setting the value to "32000". Could some one please suggest what does this warning imply and what can be the max value and what would be the impact if we increase to value beyond a say 64000.
Thanks
Dalbir
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.
Pegasystems Inc.
AU
The DSS only sets the threshold value. When the kernel level CoreMessage API, handles a message above the DSS value, then a Warning is raised.
Therefore your system is already handling message size above 64000, it’s just a matter of increasing until you stop receiving the WARNING message. Or you can ignore this Warning.