[
https://issues.apache.org/jira/browse/QPID-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282506#comment-15282506
]
Keith Wall edited comment on QPID-7255 at 5/13/16 8:06 AM:
-----------------------------------------------------------
I agree that it would be odd if the messages with delay were available for
browsing.
What would the behaviour of the feature be if the Broker or Virtualhost was
stopped for a period? Or a HA master switch? One would hope that after a
restart, the delay on any existing persistent message would continue to be
respected and be released to consumers at the publisher's originally intended
release time (or immediately if the time has already passed). I think this
implies that the Broker's store needs to be capable of storing an absolute
delayExpirationTime.
Also are there any implications for federation? Would it be the
responsibility of the Broker the first receives the message to not release the
message until the delay expires and then ensure that the message is transferred
to other Brokers in the federated network in such a way that they don't
reimpose the delay again.
was (Author: k-wall):
I agree that it would be odd if the messages with delay were available for
browsing.
What would the behaviour of the feature be if the Broker or Virtualhost was
stopped for a period? One would hope that after a restart, the delay on any
existing persistent message would continue to be respected and be released to
consumers at the publisher's originally intended release time (or immediately
if the time has already passed). I think this implies that the Broker's store
needs to be capable of storing an absolute delayExpirationTime.
> Support delivery delay
> ----------------------
>
> Key: QPID-7255
> URL: https://issues.apache.org/jira/browse/QPID-7255
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Reporter: Keith Wall
>
> Some enterprise messaging systems provide a delayed delivery feature whereby
> a publisher can provide a delivery time when sending the message, with the
> Broker taking care of not making the message available to consumers until
> that time is reached. The Java Broker should provide the same feature.
> In the Java space, JMS 2.0 has standardised this feature, however there is
> no reason why the feature could not be made available to older JMS 1.1
> clients using a Qpid specific header.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
