Using CLIENT_ACKNOWLEDGE Mode with Websphere MQ and Cache-Aside
The cache-aside database write strategy is multi-threaded. However, when Websphere MQ messages are sent using
CLIENT_ACKNOWLEDGE_MODE, each message must be handled from start to finish using a single thread. To address this issue, follow these steps:
Procedure
Define the destination using Caller’s Thread in the Threading Model setting (in the
CDD Collections tab or
Agent Classes tab).
To ensure sequential operations set the following property in the CDD file at the appropriate level:
Agent.agentClassName.enableParallelOps=false
Setting this property to false means that all post-RTC operations are done on a single thread.