Controlling the memory buffers used by a messaging engine
Every messaging engine manages two memory buffers that contain messages and message-related data. You can improve the interaction of a messaging engine with its data store by tuning the properties that set the sizes of the two buffers.
About this task
- sib.msgstore.discardableDataBufferSize
- The size in bytes of the data buffer that the messaging engine uses to contain data for which the quality of service attribute is best effort nonpersistent. The default value is 320000, which is approximately 320 kilobytes.
- sib.msgstore.cachedDataBufferSize
- The size in bytes of the data buffer that the messaging engine uses to contain data for which the quality of service attribute is better than best effort nonpersistent and that is held in the data store. 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.
Attention: The messaging engine uses approximate
calculations to manage the data it holds in the memory buffers. Neither of
the DataBufferSize properties gives an accurate indication of the amount
of memory that the messaging engine consumes in the JVM heap. The messaging
engine can consume considerably more heap storage than the DataBufferSize properties
indicate.
To set the properties of a messaging engine to improve its interaction with its data store, use the administrative console to complete the following steps:
Procedure
- In the navigation pane, click .
- Type the name of the property that you want to set.
- Type the value that you want to set for that property.
- Click OK.
- Save your changes to the master configuration.
What to do next
Remember: When you change any of these properties, the
new values do not take effect until you restart the messaging engine.