I’m not sure how it all works internally but consumers on topics do not lose incoming messages while it is busy processing one message. That would break the rule of JMS guaranteed message delivery.
I’ve had a number of projects using a topic with only one consumer on it. Normally the topic is chosen because we need to broadcast the message out and currently there’s only one interested subscriber but potentially we could add more in the future. Perfectly valid use case. On 25 Oct 2014, at 7:32 am, ddewaele <ddewa...@gmail.com> wrote: > As there is only 1 thread where a JMS Consumer is active (to avoid duplicate > msg processing), isn't it normal that messages get lost in this scenario ? > > When that thread is busy processing a message > (DefaultJmsMessageListenerContainer(AbstractPollingMessageListenerContainer).doReceiveAndExecute), > any message that comes while this JMSConsumer is active will be lost, as > this thread will close the message consumer when it's done. > > Having multiple active consumers would not help and would even make matters > worse , as you would need to deal with duplicate messages. > > In what use-case would a basic (non-virtual) activeMQ topic combined with a > single JMS consumer make sense ? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-JMS-message-topic-handling-tp5757853p5758004.html > Sent from the Camel - Users mailing list archive at Nabble.com.
