You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/02/17 16:38:00 UTC

[jira] [Work logged] (ARTEMIS-3118) Browse queue does not always show correct "Expires"

     [ https://issues.apache.org/jira/browse/ARTEMIS-3118?focusedWorklogId=553720&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-553720 ]

ASF GitHub Bot logged work on ARTEMIS-3118:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Feb/21 16:37
            Start Date: 17/Feb/21 16:37
    Worklog Time Spent: 10m 
      Work Description: brusdev opened a new pull request #3457:
URL: https://github.com/apache/activemq-artemis/pull/3457


   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.


----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 553720)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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)