Hi,
Following up on our previous message, we have looked into this issue
further.
It appears that on durable subscriber start up, it ignores the message
selector when calculating the pending queue size.
Therefore it assumes the messages from the other subscribers are for
that moment als
Hi,
We are using ActiveMQ 5.3.2, and have encountered an issue where the
"Pending queue size" values on JMX and the Admin console are incorrect,
causing a system that uses the data stored in the ActiveMQ JMX to report
incorrect information.
The problem occurs when we have multiple durable c
We have a system where we are receiving messages from a Topic using
durable subscribers. We have two durable subscribers pulling messages
off the topic 250 messages at a time and then call session.commit(). We
have found an issue where when one of the subscribers goes down
(connection is terminat
We have a system which uses a combination of a Queue and a Topic. We
create a message on server1 and put this on a Queue. Server2 then
listens on this queue (on a single consumer) and processes the messages
in multiple threads each of which posts a resulting message to a Topic
(multiple producers