All, For a Topic with multiple consumers, if one of the client is slow, it slows down other subscribers. The recommended approach is given here http://activemq.apache.org/slow-consumer-handling.html
-> approach recommended is "discarding old messages" But I don't want to discard old messages either but still want consumers running independently. http://stackoverflow.com/questions/15445941/activemq-random-slow-subscribers-causing-topic-to-full-solution One approach is shown in the above link. "keeping queues for each subscriber and now Given a Topic - pool of threads will remove events from Topic and copy the events to my queue" In my case it will be a Camel route that consumes from the Topic and publishes to a Queue (to which the Consumer pulls messages out) Does any one have suggestions on this? Does this look correct from a design point of view? (using a redundant Queue to overcome consumers impacting each other) Note: Its implicit that my source system publishes message to Topic. regards -D -- View this message in context: http://activemq.2283324.n4.nabble.com/Slow-consumer-s-impact-on-Topic-tp4666473.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
