We should avoid the expiry of the expiry because it could cause the loss of the original address/queue destination and infinite expiry loops.
Domenico On Wed, 20 Nov 2024 at 04:56, Clebert Suconic <clebert.suco...@gmail.com> wrote: > Say you set the expiry delay on the address-settings. > > > address-settings.#.expiryDelay=5000 > address-settings.#.expiryQueue=TheExpiryQueue > > > now, you send a message with an expiry delay as 2 seconds... > > > 2 seconds from now, the message expiry will move the message TheExpiryQueue > > > > > The system is currently applying 5 seconds expiry on the message > routed to TheExpiryQueue. I even open a JIRA: > https://issues.apache.org/jira/browse/ARTEMIS-5167 > > > I don't think this is correct, however an user could use the > unintended feature (aka bug) to set the expiration of the expired > message. > > > Should I avoid setting the expiry of the expiry? Does anyone see a > valid use case on such an unintended feature? > > > Currently AutoCreateExpiryResourcesTest::testWithJMSFQQN is failing > because of this. > > > > -- > Clebert Suconic > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org > For additional commands, e-mail: dev-h...@activemq.apache.org > For further information, visit: https://activemq.apache.org/contact > > >