Solution: If a filter is being used, a user trace
shows you whether this message is being evaluated as expected. The case with multiple integration servers, or multiple integration
nodes, is more complex. A response is sent to a subscriber
after the message has been processed by the target integration
server. Other integration servers (and integration nodes) are
updated asynchronously. As a result, there might be a delay
before publications made elsewhere are received. If the integration
node is busy, there can be a delay before messages are processed
fully. In a multi-integration node setup, if communications have
been suspended, subscription changes are propagated through the network
of integration nodes. Check the channels.
With multiple integration
servers or integration nodes, it might be possible to fill intermediate
WebSphere MQ queues if the load
is high. This situation might be reported in the syslog (if
an integration node cannot put to a queue because it is full)
or in the WebSphere MQ log (if a message
coming across a channel cannot be put to the target queue because
it is full). If you see messages of this type, display the
queue depths on all your queue managers to see if any are almost
full.