As I see it you have two choices: 1. Use selectors. Each broker would need to be network connected to the producer's broker with a fetch size of one message which might well limit performance but would avoid possible stuck messages. http://activemq.apache.org/selectors.html
2. Use a different queue for each different type of message. I'd do this. Far simpler provided you don't have a restriction on creating queues. James On 9 December 2010 20:39, madhavi <madhavi.sreeran...@gmail.com> wrote: > > Hi Professionals, > > I have a design query reagrding queue. My scenario is as follows > > > I have to use a messaging system, with single producer and multiple > consumers(Asynchronous). The producer pushes different types of messages > into the messaging system. Depending upon the messagetype, that particular > consumer has to consume that message.(Each consumer is running on a > different server). If, one consumer is down and a message comes for that > consumer will be in messaging system only. If, I use a message queue, the > message in the queue will block the next messages/ the next messages can be > consumed by the other consumers. Is queue suitable for handling this kind > of > situations. Or do we need to go for a topic. > Any suggestions.. > > Thanks in advance > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Query-regarding-the-working-of-a-message-queue-tp3080956p3080956.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
