MessageProcessingMaxBodySize - System Parameter
This feature was introduced to protect the user experience and prevent large messages from interrupting the business
The MessageProcessingMaxBodySize System Parameter determines how large messages Nodinite are allowed to process. Messages larger than the user defined threshold will not be processed and are evaluated as being in state Error with an additional Comment.
We at Nodinite recommend that you do NOT set a very large threshold like > 1024 MB. Your Windows Server must have plenty of RAM for larger values and you should test changes to this setting very carefully.
Management of the MessageProcessingMaxBodySize System Parameter
|System Parameter Name||Data Type||Values/Example||Comment|
|MessageProcessingMaxBodySize||integer||250 (MB)||Default =
This feature was introduced with Nodinite version 22.214.171.124
From Log Views the processing state is displayed. In the example below the top most Log Event was larger than the MessageProcessingMaxBodySize System Parameter threshold and hence was set in the Error processing state.
Example of processing states as evaluated by the MessageProcessingMaxBodySize System Parameter
Also, within the Log View an additional Comment was added by the Logging Service.
Example comment for Log Event that failed message processing due to the message size vs the value from MessageProcessingMaxBodySize System Parameter
Even further, the Nodinite Logging Service writes an entry to the Audit Log:
Example of a Audit Log entry when message processing failed due to the message size vs the value from MessageProcessingMaxBodySize System Parameter
Changing a value for any of the pre-defined System Parameters is described in the generic 'How do I change the System Parameters' article.
Then the Nodinite Logging Service will try to process the large message and depending on current load and available memory the operation may or may not succeed. Worst case is that message processing completely stops since messages are being processed in order. 1 single large message may therefor completely stop the processing of Log Events.