You're probably true. So here is my 'real' problem. I need a producer that publish let's say an event E1. I have 3 different consumers, each doing a specific task with the event E1. For each consumer, I need to find a "backup" solution if the consumer fails, i.e. to automatically "switch" to a backup consumer so that no event is lost. The backup consumer must act as if it were the master consumer; something like a durable subscriber, but a subscriber that can automatically restart on another machine with the same "identity".
No sure it's clear.............. Tom Samplonius-2 wrote: > > > ----- "ego" <[EMAIL PROTECTED]> wrote: >> ok for the queue so it's not possible for Topic consumers ? >> > > I guess, the real question is why? > > If you only want your message to go to a single consumer, why even use > topics? You requirements is for queue behavior, so I think you should use > a queue. > > Tom > > -- View this message in context: http://www.nabble.com/Kind-of-%22consumer-faliover%22-tf3828623s2354.html#a10879505 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
