Durability is only applicable when the consumers go offline. In your case, the consumer never goes offline, JMS will guarantee delivery of the message to the subscriber regardless of how slow it is consuming any prior messages. If that consumer goes offline then that’s a different story.
On 25 Oct 2014, at 6:36 pm, ddewaele <ddewa...@gmail.com> wrote: > I think messages will be delivered “at most once” and non-durable subscribers > can miss messages if they are inactive. In the case of camel, it is is a > polling consumer, meaning that > > 1. it is started > 2. it starts receiving messages (respecting timeouts) > 3. it is stopped (becomes inactive) > > According to me, when the consumer is in step 2 (processing an incoming msg) > this particular consumer will not receive any messages anymore. It needs to > exit as soon as possible so another polling consumer can pick up the next > one. If a message arrives in the meantime it will be lost. > > That's my understanding of it at least in a plain vanilla 1 thread/consumer > and plain topic setup ... please correct me if I'm wrong. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-JMS-message-topic-handling-tp5757853p5758021.html > Sent from the Camel - Users mailing list archive at Nabble.com.
