s.
I have demonstrated the use case requirements by using a Last Value Queue
with non-destructive consumers.
However, that has raised a new issue I spent the better part of today
investigating. I made a new topic for it here:
http://activemq.2283324.n4.nabble.com/Retroactive-consumer-help-td47
As was noted in the answers to your StackOverflow question, 5.x does
support retroactive consumption and Artemis does not.
Just to make sure, you would only need a new consumer to have access to the
most recent message, not any before it, right? If you need access to the
full recent history of the
The answer is pointing me in the direction of durable subscriptions. However,
to my knowledge, durable subscriptions only ensure that topics published
while a subscriber is down are received when it comes back up. Durable
subscriptions don't ensure that a late-joiner receives the latest copy of a
t
It looks like your question on Stack Overflow has been answered.
Justin
On Tue, Jul 2, 2019 at 4:12 PM mschmeiser wrote:
> I've already posted this question to Stack Overflow here:
>
> https://stackoverflow.com/questions/56858870/retroactive-consumers-in-activemq-jms-api
>
> Essentially I seem
I've already posted this question to Stack Overflow here:
https://stackoverflow.com/questions/56858870/retroactive-consumers-in-activemq-jms-api
Essentially I seem unable to get a retroactive consumer working. The
documentation is very lacking in any detail on how to actually set it up. I
create a