I know its not magic, so the QMGR for where to put the message on must be populated by the Gateway QMGR based on the clustering algorithm?
It's not wrong... it just doesn't load-balance between the two brokers in that scenario.
The flow there uses JMS, so it is always reading messages from one queue manager - regardless of which broker is running the flow. JMSInput node can read from remote qmgrs - MQInput can't.
So that qremote is designed to always send messages to one queue on one queue manager, and not designed to load-balance messages across two instances in the cluster.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum