Publish/Subscribe: Delete temporary dynamic queue

If a subscription is associated with a temporary dynamic queue, when the queue is deleted, the subscription is deleted. Publish/subscribe applications migrated from WebSphere® Message Broker are unchanged. The change does not affect the behavior of integrated publish/subscribe applications, which are written using the MQI publish/subscribe interface.

  • In IBM® WebSphere MQ 7.0, if you migrate or create a queued publish/subscribe application that uses MQRFH1, it behaves the same as IBM WebSphere MQ 6.0. You can create a temporary dynamic queue for a subscription, and if the queue is deleted, the subscription is not deleted, as in IBM WebSphere MQ 6.0. The lack of a subscriber queue results in any matching publications ending up on the dead letter queue.
  • From IBM WebSphere MQ 7.0.1, Fix Pack 6 onwards, in the same MQRFH1 queued publish/subscribe case, if the temporary dynamic queue is deleted, the subscription is deleted. This change prevents a buildup of publications from a subscription without a subscriber queue ending up on the dead letter queue.
  • From IBM WebSphere MQ 7.0 onwards, if you migrate or create a queued publish/subscribe application that uses MQRFH2, it behaves the same as WebSphere Message Broker IBM Integration Bus. You can create a temporary dynamic queue for a subscription, and if the queue is deleted, the subscription is deleted, as in IBM Integration Bus. MQRFH2 publish/subscribe applications are typically migrated from IBM Integration Bus.
  • From IBM WebSphere MQ 7.0 onwards, if you create a durable subscription using integrated publish/subscribe, you cannot define a temporary dynamic queue as the destination for its matching publications.
  • From IBM WebSphere MQ 7.0, you can create a managed, non-durable subscription using integrated publish/subscribe, which creates a temporary dynamic queue as the destination for matching publications. The subscription is deleted with the queue.

Summary

From IBM WebSphere MQ 7.0.1 onwards, you cannot create a temporary dynamic queue as the destination for publications for a durable subscription using the integrated publish/subscribe interface.

If you use either of the queued publish/subscribe interfaces, MQRFH1 or MQRFH2, the behavior is the same. You can create a temporary dynamic queue as the subscriber queue, and if the queue is deleted, the subscription is deleted with it.