|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
WBI MB Pub Sub Trap detection |
« View previous topic :: View next topic » |
Author |
Message
|
sanu_mit |
Posted: Fri Mar 04, 2005 12:24 pm Post subject: WBI MB Pub Sub Trap detection |
|
|
Apprentice
Joined: 03 Jul 2003 Posts: 25 Location: Kolkata
|
Hi,
My message flow publishes a message after processing. Now there are other message flows which may or may not subscribe to this publication. Now I want to store a copy of the output message if and only if corresponding publication is not subscribed by anyone else. How do I achieve this?
Any suggestion in this regard is highly appreciated.
Thanks & regards,
Sanu. |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Mar 04, 2005 12:39 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I doubt you can do this.
In order to do this, you would have to subscribe.
Then someone would be subscribed.
Or you would have to know how the Pub/Sub broker stores subscriptions.
But you should not care how the Pub/Sub broker stores it's subscriptions - because what happens if the broker changes the way it does this? Or you change brokers?
Publishers are SUPPOSED to be independant from subscribers. This is also true of subscribers from each other - nobody in a pub/sub network should care if anyone else is there.
You need to reconsider your requirements. Why not just store all publications? If space is an issue, then you can schedule automatic tasks to clean up publications after x period of time. Or you could have each of your subscribers publish an event that they got a subscription... and then have a subscriber to that event... But then, what if that subscriber wasn't available? Here we go round again... _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
sanu_mit |
Posted: Fri Mar 04, 2005 12:46 pm Post subject: |
|
|
Apprentice
Joined: 03 Jul 2003 Posts: 25 Location: Kolkata
|
Actually my requirement is to have a type of audit to ensure that all messages rightly pass out from the source system to the target system and we have hundreds of thousands of messages passing through the system round the time. So subscribing to all the messages might not be a good idea to detect the specific one which failed to get a subscriber.
Any idea as to how this audit mechanism can be implemented is highly appreciated.
Thanks & regards,
Sanu. |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Mar 04, 2005 2:15 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Monitor the queue depth on the publication broker's input queue.
If that ever piles up, then the broker isn't processing publications... _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|