Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
5.9.0, 5.9.1, 5.10.0
-
None
Description
AS IS
JMS Consumer re-checks messages served to him by the Broker and ignores those appearing to be expired according to the clock on the Consumer machine.
TO BE
Allow Consumer to optionally disable this check and blindly trust the expirations check already performed at the Broker, according to the broker clock.
RATIONALES
When the Consumer clock is running ahead of the Broker clock by more that the time-to-live of a message, the message would be wrongly ignored by the consumer.
Please notice that in a situation like this BrokerTimestampingPlugin is of no help, because it only influence the way messages sent by the Producer are handled at the broker, while the issue reported here is Consumer related.
ADDITIONAL RATIONALES
1\ STOMP API does NOT perform expiration re-checks at the consumer (and this is good)
2\ .NET API already has an option as the one request here and for similar reasons
BACKGROUND DISCUSSION
Here are some snippets of the background discussion on users@activemq.apache.org list, where this request has been informally seconded by Gary Tully & Timothy Bish (thanks guys!):
http://mail-archives.apache.org/mod_mbox/activemq-users/201410.mbox/%3CCANGe49ckNM-6_DiYWVTtDfgAZPJ2SJoMc3ypJF7K+VsBdoUaVA@mail.gmail.com%3E
http://mail-archives.apache.org/mod_mbox/activemq-users/201410.mbox/%3CCAFitrpQJK4MukyJ5yxPb=ygQnC0yV5jetgWiesxu8BqagfSScQ@mail.gmail.com%3E
http://mail-archives.apache.org/mod_mbox/activemq-users/201410.mbox/%3CCANGe49c0Xok732URRZKAx0__H9XVqjys_7auE5ysH0um+4fZkQ@mail.gmail.com%3E
http://mail-archives.apache.org/mod_mbox/activemq-users/201410.mbox/%3CCAH+vQmPtedrsomaZsvzU+eksLEm6GGeO5p=QzYPtqwB7ArvgAw@mail.gmail.com%3E
http://mail-archives.apache.org/mod_mbox/activemq-users/201410.mbox/%3C5447BF6F.1090103@gmail.com%3E
Attachments
Issue Links
- is related to
-
AMQCPP-575 Add support for disable of expiration checks in MessageConsumer
-
- Resolved
-