[
https://issues.apache.org/jira/browse/ARTEMIS-3118?focusedWorklogId=556397&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-556397
]
ASF GitHub Bot logged work on ARTEMIS-3118:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Feb/21 15:30
Start Date: 23/Feb/21 15:30
Worklog Time Spent: 10m
Work Description: cshannon opened a new pull request #3465:
URL: https://github.com/apache/activemq-artemis/pull/3465
Other protocols besides CORE may not have a metadata map so we need to
check for null before passing to the filter matcher
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 556397)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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)
