Use this task to set tuning properties for the service integration environment by editing the sib.properties file
Properties for a messaging engine
Name | Value |
---|---|
sib.processor.blockedRetryTimeout | The messaging engine custom property sib.processor.blockedRetryTimeout
tells the application server how long to wait before re-delivering a message
to an MDB, if and only if the exception destination property is set to None
and the configured number of maximum failed deliveries has been reached. The default value is 5000 milliseconds, which equates to 5 seconds. Any messages that are rolled back after the maximum failed deliveries limit will therefore remain on the original destination for 5 seconds before they are re-delivered to an MDB. |
sib.trm.retry | The messaging engine to messaging engine connection retry interval in seconds. The retry interval is the time delay left between attempts to contact neighboring messaging engines with which communications that exist. The default retry interval is 30 seconds. |
Properties for the component of a messaging engine that manages the data store
Name | Value |
---|---|
sib.msgstore.discardableDataBufferSize | The size in bytes of the data buffer used by the messaging engine to
contain data for which the quality of service attribute is best effort nonpersistent.
The messaging engine holds this data
entirely within this memory buffer and never writes this data to the data store.
When the messaging engine adds data
to this buffer, for example when the messaging engine receives
a best effort nonpersistent message from a client,
the messaging engine might discard
data already in the buffer to make space. This behavior enables the messaging engine to
discard best effort nonpersistent messages. The discardable data buffer contains all data for which the quality of service attribute is best effort nonpersistent. That data comprises data both that is involved in active transactions, and any other best effort nonpersistent that the messaging engine has neither discarded nor consumed. The messaging engine can discard only data that is not involved in active transactions. Tip: If
the messaging engine attempts to
add data to the discardable data buffer when insufficient space remains after
discarding all the data that is not involved in active transaction, the messaging engine throws a com.ibm.ws.sib.msgstore.OutOfCacheSpace exception.
Client applications can catch this exception, wrapped inside API-specific
exceptions such as javax.jms.JMSException.
The sib.msgstore.discardableDataBufferSize property of the messaging engine controls the size of the discardable data buffer. You specify the value of this property in bytes. The default value is 320000, which is approximately 320 kilobytes. |
sib.msgstore.cachedDataBufferSize | The size in bytes of the data buffer used by the messaging engine to
contain data for which the quality of service attribute is better than best effort nonpersistent and which is held in the data store. The purpose of the
cached data buffer is to optimize the performance of the messaging engine by
caching in memory the data that the messaging engine might
otherwise need to read from the data store.
As it writes data to the data store and
reads from the data store,
the messaging engine attempts to
add that data to the cached data buffer. The messaging engine might
discard data already in the buffer to make space. The sib.msgstore.cachedDataBufferSize property of the messaging engine controls the size of the cached data buffer. You specify the value of this property in bytes. The default value is 320000, which is approximately 320 kilobytes. |
sib.msgstore.transactionSendLimit | The maximum number of operations that the messaging engine includes in each transaction. For example, each JMS send or receive is an operation that counts towards the transaction send limit. The default value is 100. |
Properties
for the delivery of messages to message-driven beans
Name | Value |
---|---|
sib.ra.zosMessageLockTimeout | The number of seconds that a message is locked in the messaging engine
after that message has been submitted to Workload management (WLM) for z/OS
for delivery to a message-driven bean. WLM allocates the message to a servant region, which creates a connection to the messaging engine. The servant region then consumes the message and passes it to the onMessage method of the message-driven bean. If the servant region fails to connect to the messaging engine and consume the message before passing it to the message-driven bean, the message remains unlocked until the timeout value is reached. When the timeout is reached, the message is unlocked and delivery is retried. During startup of an application server, if WLM delivers a message to a servant region before the infrastructure that is required to connect to the messaging engine is available, that servant region might fail to connect to a messaging engine. Connection failures of this type are indicated by CWSIV1052W entries in the job log of the servant region. If you see such entries in the job log, and you have locked messages, consider using this property to make the Message Lock Timeout shorter. The value for this property is fixed at 300 seconds. |
To set these properties by editing the sib.properties file, perform the following steps: