qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-7568) [Java Broker] [AMQP 1.0] support Delayed Delivery with the JMS 2.0 client
Date Fri, 02 Dec 2016 15:32:58 GMT

     [ https://issues.apache.org/jira/browse/QPID-7568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robbie Gemmell updated QPID-7568:
---------------------------------
    Description: 
QPID-7255 added a form of delayed delivery support for the Java broker and AMQP 0-X JMS client,
with a qpid specific annotation in the case of AMQP 1.0. The AMQP 1.0 JMS client will also
support this via addition of support for JMS 2.0 (QPIDJMS-207), but with some differences
than in QPID-7255, and it would be good for the Java broker to support this too.

The JMS 2.0 client can detect server support for the functionality in two ways:
- by the server offering a "DELAYED_DELIVERY"  connection capability
- or, if the connection capability wasn't offered, by setting a desired capability of "DELAYED_DELIVERY"
on the sending link attach and inspecting if it is offered in the response.

If support for delivery delay was identified, when sending a message with a producer configured
with a delivery delay, the message will carry a MessageAnnotation with _"x-opt-delivery-time"_
symbol key and long value representing the time at which the message can be delivered to receivers
as the number of milliseconds since the epoch. If support was not identified, the send will
fail in order to reflect that the requested delay/delivery-time can't be satisfied.

  was:
QPID-7255 added a form of delayed delivery support for the Java broker and AMQP 0-X JMS client,
with a qpid specific annotation in the case of AMQP 1.0. The AMQP 1.0 JMS client will also
support this via addition of support for JMS 2.0 (QPIDJMS-207), but with some differences
than in QPID-7255, and it would be good for the Java broker to support this too.

The JMS 2.0 client can detect server support for the functionality in two ways:
- by the server offering a "DELAYED_DELIVERY" connection capability
- or, if the connection capability wasn't offered, by setting a desired capability of "DELAYED_DELIVERY"
on the sending link attach and inspecting if it is offered in the response.

If support for delivery delay was identified, when sending a message with a producer configured
with a delivery delay, the message will carry a MessageAnnotation with "x-opt-delivery-time"
Symbol key and long value representing the time at which the message can be delivered to receivers
as the number of milliseconds since the epoch. If support was not identified, the send will
fail in order to reflect that the requested delay/delivery-time can't be satisfied.


> [Java Broker] [AMQP 1.0] support Delayed Delivery with the JMS 2.0 client
> -------------------------------------------------------------------------
>
>                 Key: QPID-7568
>                 URL: https://issues.apache.org/jira/browse/QPID-7568
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Robbie Gemmell
>
> QPID-7255 added a form of delayed delivery support for the Java broker and AMQP 0-X JMS
client, with a qpid specific annotation in the case of AMQP 1.0. The AMQP 1.0 JMS client will
also support this via addition of support for JMS 2.0 (QPIDJMS-207), but with some differences
than in QPID-7255, and it would be good for the Java broker to support this too.
> The JMS 2.0 client can detect server support for the functionality in two ways:
> - by the server offering a "DELAYED_DELIVERY"  connection capability
> - or, if the connection capability wasn't offered, by setting a desired capability of
"DELAYED_DELIVERY" on the sending link attach and inspecting if it is offered in the response.
> If support for delivery delay was identified, when sending a message with a producer
configured with a delivery delay, the message will carry a MessageAnnotation with _"x-opt-delivery-time"_
symbol key and long value representing the time at which the message can be delivered to receivers
as the number of milliseconds since the epoch. If support was not identified, the send will
fail in order to reflect that the requested delay/delivery-time can't be satisfied.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message