activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jdanekrh <>
Subject [GitHub] activemq-artemis issue #1407: ARTEMIS-1276 fix JmsSendReceiveWithMessageExpi...
Date Wed, 19 Jul 2017 17:36:27 GMT
Github user jdanekrh commented on the issue:
    > messages only expire on client on activemq5 while it's on server & client on
    Did you mean expire on _server_ on activemq5? If it expired on client, how would it then
get to DLQ queue on server?
    I think get it now. When the test receives for the first time (first `for` loop), the
client gets first 10 messages sent, which are those with short expiration time. One of them
is delivered ok, the 9 remaining expire on the client while it is in sleep(). That means these
9 never get into the DLQ, because for that they would have to expire on the server. Which
explains the `actual: 90, expected: 99` result when it is then receiving from DLQ.
    I did not know about this difference between 5 and Artemis.
    From user point of view, the fact that prefetch changes behavior (and is not just performance
optimization) and that it can cause what can be thought of as a message loss (these 9 messages
have irrevocably disappeared, right?) could be considered a bug, I think.
    I guess there is nothing to be done about it here, so removing [wip].

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message