[
https://issues.apache.org/jira/browse/ARTEMIS-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286135#comment-17286135
]
ASF subversion and git services commented on ARTEMIS-3118:
----------------------------------------------------------
Commit ab7058ac7531c3522bd85dd25b003ea765d45c74 in activemq-artemis's branch
refs/heads/master from Domenico Francesco Bruscino
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=ab7058a ]
ARTEMIS-3118 Fix the expiration on converting from AMQP to core
Initialize the JMS expiration with the value calculated during the scan
of the AMQP message to avoid a different value for each conversion based
on System.currentTimeMillis() and ttl.
> 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: 10m
> 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)
