Every subscriber needs to have its own queue On Mon, Nov 23, 2009 at 1:26 PM, Andrew <[email protected]> wrote:
> I am trying to set up pub-sub between 1 publisher and multiple > subscribers using Rhino Service Bus. However, all I ever seem to get > is competing consumers (where messges are distributed between 1 > consumer or the other, but not sent to both). > > My current publisher configuration looks like this (Note: I'm using > the new OnewayRhinoServiceBusFacility so I don't need to define a bus > element in the sender) > > <facility id="rhino.esb.sender" > > <messages> > <add name="My.Messages.Namespace" > endpoint="msmq://localhost/my.queue"/> > </messages> > </facility> > > My subscriber configuration looks like this: > > <facility id="rhino.esb.receiver" > > <bus threadCount="1" numberOfRetries="5" endpoint="msmq:// > localhost/my.queue" DisableAutoQueueCreation="false" /> > <messages> > <add name="My.Messages.Namespace" endpoint="msmq:// > localhost/my.queue" /> > </messages> > </facility> > > This works fine and dandy for 1 publisher and 1 subscriber. However, > what I want to acheive is 2 subscribers listening to the same message > and each receiving their own copy of the message. So, I just copied > and pasted the subscriber exe and config file file to create my second > subscriber. I've tried various config settings but no matter what I > do, I only end up with competing consumers. > > I would've assumed that I could define a different endpoint for each > receiver bus (and leave the messages element above still pointing to > "msmq://localhost/my.queue"). In this way, each receiver can have > their own queue. I.e. the configuration for the subscriber looks like: > > <facility id="rhino.esb.receiver" > > <bus threadCount="1" numberOfRetries="5" endpoint="msmq:// > localhost/my.subscriber1" DisableAutoQueueCreation="false" /> > <messages> > <add name="My.Messages.Namespace" endpoint="msmq:// > localhost/my.queue" /> > </messages> > </facility> > > But, if I try to do this, I don't receive any messages at all (even > though from the log files, it looks like it's doing the right thing). > > This must be possible so I'm sure I've missed something obvious here. > Any help much appreciated. > > Cheers > > -- > > You received this message because you are subscribed to the Google Groups > "Rhino Tools Dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rhino-tools-dev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rhino-tools-dev?hl=. > > > -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
