ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » pub/sub and message transactionality

Post new topic  Reply to topic
 pub/sub and message transactionality « View previous topic :: View next topic » 
Author Message
jonny
PostPosted: Wed Feb 02, 2005 9:07 am    Post subject: pub/sub and message transactionality Reply with quote

Acolyte

Joined: 03 Jul 2003
Posts: 57

Hi,

When using the publication node in WBIMB V5 CSD03 on Solaris, and if there is more than one subscribers to the topic being published, I have noticed that if one of the subsription queues is not available (put inhibited, not authorized , etc) messages will still be put onto the other subscription queues. I have transaction mode of the Input node set to 'Yes', messages for the non available queue went to the DEAD letter queue.

Questions:

1)- How can I achieve all or nothing (transactionality) using pub/sub
2)- Is it a norma behaviour for the publication mode, if it couldn't put a message to one of its subscription queues that the message will go to the DEAD letter queue, even though I have the catch and failure terminals of the input node wired.

Thanks
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Feb 02, 2005 9:14 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

The whole point of pub/sub is that the publisher is independant from the subscribers AND the subscribers are independant from each other.

You can't do what you want with pub/sub.

And you likely should reconsider your design in general. You may be able to accomplish what you appear to want with aggregation rather than pub/sub. But you likely don't want to be doing what you appear to want to do - at least in Broker (workflow may be more suited).

As for your question 2, this is what happens. The publisher puts the message on one queue - the control queue of the publication engine. The publication engine then creates a copy of the message for each registered subscriber. If a subscriber queue is unavailable, that individual subscription message goes to the Dead Letter Queue in normal processes.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » pub/sub and message transactionality
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.