a time
sync difference greater than the TTL the broker stopped dispatching messages
to the consumer.
Has anyone else seen a similar problem?
davery wrote
I was able to reproduce the problem and get a stack trace for the hanging
thread. It appears to be waiting for data from the ActiveMQ broker
Client side ack is set to auto acknowledge
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-consumers-stop-accepting-messages-tp4678923p4679008.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
message.acknowledge() every now and then?
On 13 March 2014 15:52, davery [hidden
email]/user/SendEmail.jtp?type=nodenode=4679023i=0 wrote:
Client side ack is set to auto acknowledge
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-consumers-stop-accepting
.
On 13 March 2014 16:47, davery lt;
d_avery@
gt; wrote:
No, I didn't think that was required when the session is in auto
acknowledgement mode.
From: gtully [via ActiveMQ] [mailto:
ml-node+s2283324n4679023h49@.nabble
]
Sent: Thursday, March 13, 2014 9:41 AM
To: Avery, Dave
Subject
Hi,
I have two ActiveMQ 5.8 instances setup in a network of brokers. Each
instance is hosted on a separate machine running Ubuntu 12.04 with 8GB of
memory. After one week in production, we started seeing consumers that
wouldn't accept messages. In the web console I can see the messages enqueue
