You're welcome to submit an enhancement request in JIRA for this. I think
it would be a useful feature.
Tim
On Thu, Nov 15, 2018, 2:47 PM ncasaux Problem occurred again on a queue 3 days after it was created and no
> consumer
> at all. ActiveMQ finally shut down due to not enough space on the ma
FWIW, ActiveMQ Artemis supports message expiration on the broker without a
consumer via the "expiry reaper thread" [1]. I realize you may not be able
to update your ActiveMQ broker, but I thought it was worth presenting the
option.
Justin
[1] https://activemq.apache.org/artemis/docs/latest/mess
Problem occurred again on a queue 3 days after it was created and no consumer
at all. ActiveMQ finally shut down due to not enough space on the machine.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
It's my understanding (from what others have written on this mailing list,
not from checking the code) that message expiration is checked twice: once
broker-side when the message is dispatched to the consumer (or queue
browser), and once client-side when the message is taken from the front of
the p
Hello,
I have a configuration with one virtualtopic and three queues.
I send multiples messages on the virtualtopic and they all have a expiration
date.
Sometime, when the queue has no consumer, the expired messages on the queue
are not removed properly and remain on the queue, but this does not
