Limitations of the MQ binding

Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
Draft comment:
This topic was viewed 3 times since its publication
The MQ binding has some limitations in its use that are listed here.

No publish-subscribe message distribution

The publish-subscribe method of distributing messages is not currently supported by the MQ binding though WMQ itself supports publish-subscribe. However, the MQ JMS binding does support this method of distribution.

Shared receive queues

Multiple WebSphere® MQ export and import bindings expect that any messages present on their configured receive queue are intended for that export or import. Import and export bindings should be configured with the following considerations:
  • Each MQ import must have a different receive queue because the MQ import binding assumes all messages on the receive queue are responses to requests that it sent. If the receive queue is shared by more than one import, responses could be received by the wrong import and will fail to be correlated with the original request message.
  • Each MQ export should have a different receive queue, because otherwise you cannot predict which export will get any particular request message.
  • MQ imports and exports can point to the same send queue.