Provide reaper thread to implement timeToLive
----------------------------------------------
Key: QPID-499
URL: https://issues.apache.org/jira/browse/QPID-499
Project: Qpid
Issue Type: Improvement
Affects Versions: M2
Reporter: Martin Ritchie
Fix For: M3
The timeToLive parameter is available on some of the send methods of the
javax.jmx.MessageProducer interface and thus on the qpid implementation
(org.apache.qpid.client.BasicMessageProducer) of this interface. However, this
flag is not actually implemented i.e. currently just ignored :-(
We need to implement support for this parameter. This requires a check on the
AMQP protocol handling of this flag i.e. to check that it can currently be
supported. Think it is - but implementer to check and raise if not.
The information below has been extracted from section 4.8 of the JMS
specification fyi (see spec for more detail/refs):
A client can specify a time-to-live value in milliseconds for each message it
sends. This value defines a message expiration time that is the sum of the
message's time-to-live and the GMT it is sent (for transacted sends, this is
the time the client sends the message, not the time the transaction is
committed). A JMS provider should do its best to expire messages accurately;
however, JMS does not define the accuracy provided. It is not acceptable to
simply ignore time-to-live.
For more information on message expiration, see Section 3.4.9 "JMSExpiration."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
