Message handling configuration properties for JMS errors, message size, and documentation suppression

Configure properties in the 100Custom.xml file to control JMS error propagation, message size limits, and documentation suppression in monitor events.

About this task

The following configuration properties can be added to the 100Custom.xml file to avoid errors in the JMS queue.

<common>
   <monitor-event-emission>
      <propagate-jms-error merge="replace">false</propagate-jms-error>
      <message-size-limit merge="replace">800000</message-size-limit>
      <suppress-documentation-in-message merge="replace">true</suppress-documentation-in-message> 
   </monitor-event-emission>
</common>

propagate-jms-error: Controls whether to propagate JMS errors back to the engine. The valid values are true or false, and the default value is false.
Note: If the value is false, the error is not propagated to the engine, but a message is logged. There is the potential to lose the message if deleted from queue. If the value is true, an error is propagated which fails the engines.
message-size-limit: Sets the size of the message that is allowed on the JMS queue. If the message is too large, an exception is triggered. The value is the size in bytes. The valid value is any positive integer, and the default value is 800000.
Note: This property prevents the message size from getting too large. Kafka can only process messages to a certain limit that depends on your Kafka. If the message size is larger than what Kafka can process, it fails and remains in the JMS queue, never to be processed.
suppress-documentation-in-message: Prevents the process and process app documentation from being included in the def events. The valid values are true or false, and the default value is true.