I'm much more familiar with debugging the broker than the client, so I
don't know exactly how to look into the client to see what state it's in
(whether the missing messages are sitting in memory or were never received,
what the threads are doing, etc.). I'd start by taking a thread dump and a
mem
Hi,
I forgot to mention one point. We recently upgraded to ActiveMQ-5.11.1. And
only after this upgrade, we saw this issue.
We have encountered this twice. Can some one please check or atleast let me
know if there were some changes related to this in 5.11.1
Details:
> Suddenly a consumer stop
Hi Tim,
Yes. 3 consumers were connected to that topic out of which two were durable
and one(this) was non-durable.
I have jconsole monitoring for the broker and from jconsole I can see that
all enqueued message were received by the durable consumers but some
messages were missing for non-durable
p:subscriptionDurable="false"
> p:sessionAcknowledgeModeName="AUTO_ACKNOWLEDGE"
> p:sessionTransacted="true"
> p:messageListener-ref="testconsumer"
> />
>
> Thanks,
> Anuj
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-topic-Messages-are-not-delived-to-a-client-tp4695554.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-topic-Messages-are-not-delived-to-a-client-tp4695554.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
