[
https://issues.apache.org/jira/browse/ARTEMIS-5142?focusedWorklogId=945700&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-945700
]
ASF GitHub Bot logged work on ARTEMIS-5142:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 26/Nov/24 12:26
Start Date: 26/Nov/24 12:26
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #5334:
URL:
https://github.com/apache/activemq-artemis/pull/5334#issuecomment-2500663688
Also, I noticed the regular expiry-delay (not min/max) setting has the same
'0 makes it set expire now' behaviour because it will set the current time as
the expiration. It is subtly different from the min/max case in that the
setting only ever applies to messages with an existing expiration, so setting
expiry-delay to 0 really makes no sense to begin with, so it could more
reasonably just be left as it is, but I wonder if it should also special-case
it like min/max now do?
Issue Time Tracking
-------------------
Worklog Id: (was: 945700)
Time Spent: 4h 40m (was: 4.5h)
> Setting 0 for min/max expiry-delivery not working as expected
> -------------------------------------------------------------
>
> Key: ARTEMIS-5142
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5142
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Labels: pull-request-available
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> If {{max-expiry-delay}} or {{min-expiry-delay}} is set to {{0}} messages are
> expired _immediately_ rather than not expired at all as expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
