[
https://issues.apache.org/jira/browse/ARTEMIS-5142?focusedWorklogId=943379&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-943379
]
ASF GitHub Bot logged work on ARTEMIS-5142:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Nov/24 16:10
Start Date: 12/Nov/24 16:10
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #5334:
URL:
https://github.com/apache/activemq-artemis/pull/5334#issuecomment-2470947324
In addition to the above comments on potential for mismatch between doc
and/or expectations and the actual behaviour...I pushed another commit with
some more tests, and tweaks to some of the existing tests, to more strictly
verify the resulting expiration value set is in the expected range. See what
you think.
Issue Time Tracking
-------------------
Worklog Id: (was: 943379)
Time Spent: 2h (was: 1h 50m)
> 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: 2h
> 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
