[
https://issues.apache.org/jira/browse/ARTEMIS-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286761#comment-17286761
]
Erwin Dondorp commented on ARTEMIS-3118:
----------------------------------------
Domenico,
Thanks for fixing this.
I'm using "a", see https://github.com/fmtn/a
My application transports a lot of measurement data; so options like TTL and
also non-persistence are important for me.
And I typically also use TTL=1min during testing so that I have a lot less
cleaning to do.
But production loads may even use shorter TTLs, sometimes down to 5s. We might
change some of these into LVQs later.
> Browse queue does not always show correct "Expires"
> ---------------------------------------------------
>
> Key: ARTEMIS-3118
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3118
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 2.16.0
> Reporter: Erwin Dondorp
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When sending message with a TTL of 5 minutes (300000 millis), the "Browse
> Queue" screen always initially shows (Expires) "in 00:04:59". Even when that
> screen is visited multiple seconds after sending the message. The screen can
> then be seen decrementing the value each 10 seconds. But when the browser
> screen is refreshed, the timer starts again with "in 00:04:59".
> The effect occurs only for TTL > 60 seconds.
> After the original TTL has passed, the messages are always properly expired.
> So the messaging layer seems ok.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
