Properties Related to Synchronous Messages

messaging.syncMessageRemover.checkInterval

Value: Minutes

Default: 5

The messaging system keeps the message header for synchronous messages in the memory for monitoring purposes. The payload of the message is immediately removed to save resources (this behavior can be configured by the removeBody property), as soon as the message reaches a final state.

The property specifies how often the synchronous-message-remover job in the messaging system checks for synchronous messages that have reached a final state and can therefore be completely removed from memory.

You can modify this property online.

messaging.syncMessageRemover.messageCount

Value type: Integer

Default: 1000

This property defines the maximum number of synchronous message headers that are kept in memory for monitoring and duplicate detection purposes. The synchronous-message-remover job checks how many messages are in final state and could be completely removed from memory.

Then it removes the oldest synchronous message headers until a maximum number of message headers are left in memory, as configured by the messageCount property

You can modify this property online..

messaging.syncMessageRemover.removeBody

Value type: Boolean

Default: true

The messaging system removes the payload of synchronous messages by default as soon as they reach a final state. This feature can be disabled to allow the message body to be analyzed in the case of errors (also for synchronous messages) by using this property.

This property must only be changed for extended error analysis. Keeping all message bytes of synchronous messages in the memory can lead to OutOfMemoryErrors in AS Java.

You can modify this property online.