Properties Related to the Messaging System

The Following Properties are Related to the Messaging System

Name

Description

messaging.initial.delay

messaging.startup.delay

Values are time periods in milliseconds

Default for both properties: 0

These properties must not be changed for the SAP J2EE Engine.

In the case of other J2EE engines, it may be necessary to delay the initialization and startup up the messaging system in order to wait for the startup of required resources, such as the data source of the transaction manager and so on.

messaging.system.transactionManager

Default value for the SAP J2EE Engine: ts

JNDI name of the J2EE engine transaction manager.

This property must not be changed for the SAP J2EE Engine.

messaging.system.failNonDelivered

Value type: Boolean

Default: false

This property specifies whether asynchronous messages should automatically be set to failed, once the maximum amount of retries is exceeded.

The default value is false, so that messages in state Not Delivered have to be manually set to failed as part of an administrator task in message monitoring.

messaging.system.lazyInit

Value type: Boolean

Default: false

This property is obsolete and will be removed in a future release.

messaging.syncMessageRemover.checkInterval

Value: Minutes

Default: 60

The messaging system keeps the message header for synchronous messages in the memory for monitoring and duplicate detection 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.

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.

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 the SAP J2EE Engine.

messaging.persistMessageRemover.checkInterval

Value is in minutes

Default: 1440 (1 day)

The messaging system tries to remove persisted (asynchronous) messages with an expired persist duration from the database at system startup and then periodically during the configured time interval. The default value is once per day.

The persist duration of XI messages can be configured by properties in the J2EE service SAP XI AF Adapter: XI, where the default value is 30 days. The persist-duration properties for the XI messages may need to be decreased at times of heavy message throughput to avoid that the database volume limitation being reached before the predefined default value of 30 days.

messaging.cluster.timeout

Value is in milliseconds.

Default: 60000 (1 minute)

This property specifies the timeout value for the cluster communication in the SAP J2EE Engine. Even though the default value of one minute should be sufficient, this value may be increased in cases where you are experiencing cluster timeout exceptions of the cluster communication mechanism of the J2EE Engine.

messaging.system.node

Value type: Integer

No default.

Defines the cluster node ID.

In the SAP J2EE Engine environment, this property is automatically set at system startup and must not be changed.

messaging.debug

Currently supported values are: HTTP and SSL

Default: HTTP

This property enables extended debugging statements in the trace file for the message body (extended transport level debugging).