[
https://issues.apache.org/jira/browse/QPID-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277801#comment-15277801
]
Rob Godfrey commented on QPID-7255:
-----------------------------------
I don't see why an operator wouldn't be able to delete the message.
A different question: would the message be available for browsing - my sense is
not...
I'm thinking that the implementation of this is that any such "held" message is
treated as "acquired" by a "holding actor" within the broker. Whenever a
consumer attempts to acquire a message the message checks to see if it should
be held (if it is not already) or if it should be released (if it is currently
held). Secondly the housekeeping process would cause the hold/release from
hold check to be run against all messages in the queue.
> 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]
