Perform this task as part of
Investigating why publish/subscribe messages are not arriving at a subscription.
This task explains how to investigate the flow of messages in a publish/subscribe
messaging scenario where the messages are being routed through a remote message
point to a nondurable subscription. The following diagrams illustrates two
possible situations. The dotted lines in the diagrams indicate relationships
between publication points, whereas the solid lines indicate flow of messages.
In Figure 1, ME1 is the messaging engine that the producing application is
attached to, and ME2 and ME3 are the messaging engines that are hosting the
subscriptions. The publication points on ME2 and ME3 are represented by remote
publication points on ME1. In Figure 2, Subscribing application B, which is
attached to ME3, has a durable subscription which receives messages through
ME2, rather than directly from ME1. In order to do this, ME3 hosts a remote
subscription, which represents the subscription on ME2. The messaging engines
are referred to in the following steps.
Figure 1. Point-to-point message
production using a remote message point
Figure 2. Publish/subscribe messaging using a remote message point
The following steps apply to both the above scenarios.