[
https://issues.apache.org/jira/browse/ARTEMIS-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Danner updated ARTEMIS-3281:
--------------------------------------
Description:
When an address has an expiry-delay defined it will be correctly applied
whenever a message is routed to it that has the default expiration delay set.
This is also correctly shown in the Artemis web console.
However, after the broker is restarted all messages that had an expiration time
set are suddenly displayed without any expiration time set (i.e the default
value of 1970-01-01 01:00:00 is shown and the "expiration" header in the
message detail view shows an incorrect value of 0 as well).
Changing the expiry-delay to a very small value for testing purposes has shown
that the messages do indeed expire after the configured time, so this seems to
be a display issue only.
The attached screenshots show an example before and after restart.
This behavior is reproducible 100% of the time.
was:
When an address has an expiry-delay defined it will be correctly applied
whenever a message is routed to it that has a default expiration delay set.
This is also correctly shown in the Artemis web console.
However, after the broker is restarted all messages that had an expiration time
set are suddenly displayed without any expiration time set (i.e the default
value of 1970-01-01 01:00:00 is shown and the "expiration" header in the
message detail view shows an incorrect value of 0 as well).
Changing the expiry-delay to a very small value for testing purposes has shown
that the messages do indeed expire after the configured time, so this seems to
be a display issue only.
The attached screenshots show an example before and after restart.
This behavior is reproducible 100% of the time.
> Displayed message expiration incorrect after broker restart
> -----------------------------------------------------------
>
> Key: ARTEMIS-3281
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3281
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 2.17.0
> Reporter: Christian Danner
> Priority: Major
> Attachments: expired_detail_610894.PNG,
> expired_detail_610894_after_restart.PNG, expired_overview.PNG,
> expired_overview_after_restart.PNG
>
>
> When an address has an expiry-delay defined it will be correctly applied
> whenever a message is routed to it that has the default expiration delay set.
> This is also correctly shown in the Artemis web console.
> However, after the broker is restarted all messages that had an expiration
> time set are suddenly displayed without any expiration time set (i.e the
> default value of 1970-01-01 01:00:00 is shown and the "expiration" header in
> the message detail view shows an incorrect value of 0 as well).
> Changing the expiry-delay to a very small value for testing purposes has
> shown that the messages do indeed expire after the configured time, so this
> seems to be a display issue only.
> The attached screenshots show an example before and after restart.
> This behavior is reproducible 100% of the time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
