qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-7603) [AMQP 1.0] Maximum Delivery Count/Dead-lettering
Date Wed, 04 Jan 2017 17:33:58 GMT

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

Keith Wall updated QPID-7603:
-----------------------------
    Description: 
Placeholder for Maximum Delivery Count/Dead-lettering support.

The current implementation in the Broker is incomplete.  I notice the following areas.  There
may be more.

* The protocol layer needs to trigger the MessageInstance#routeToAlternate
* Handling of the {{Rejected}} outcome is absent. http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-rejected
* Implement handling of default outcomes.
* AMQP 1.0 Conversion layer should set Header#setDeliveryCount()
* I note that the AMQP 0-8..0-10 protocol layers use the MessageInstance#deliveryCount differently
to the AMQP 1.0 protocol layer.    This will need some care to ensure that protocol's play
nicely together.

Also verify:

* Behaviour when the session is rolled back or the recovered.
* Behaviour when the session or connection is closed.
* Behaviour when the connection is abruptly dropped.



  was:
Placeholder for Maximum Delivery Count/Dead-lettering support.

The current implementation in the Broker is incomplete.  I notice the following areas.  There
may be more.

* The protocol layer needs to trigger the MessageInstance#routeToAlternate
* Handling of the {{Rejected}} outcome is absent. http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-rejected
* Implement handling of default outcomes.
* AMQP 1.0 Conversion layer should set Header#setDeliveryCount()
* I note that the AMQP 0-8..0-10 protocol layers use the MessageInstance#deliveryCount differently
to the AMQP 1.0 protocol layer.    This will need some care to ensure that protocol's play
nicely together.




> [AMQP 1.0] Maximum Delivery Count/Dead-lettering
> ------------------------------------------------
>
>                 Key: QPID-7603
>                 URL: https://issues.apache.org/jira/browse/QPID-7603
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Keith Wall
>             Fix For: qpid-java-7.0
>
>
> Placeholder for Maximum Delivery Count/Dead-lettering support.
> The current implementation in the Broker is incomplete.  I notice the following areas.
 There may be more.
> * The protocol layer needs to trigger the MessageInstance#routeToAlternate
> * Handling of the {{Rejected}} outcome is absent. http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-rejected
> * Implement handling of default outcomes.
> * AMQP 1.0 Conversion layer should set Header#setDeliveryCount()
> * I note that the AMQP 0-8..0-10 protocol layers use the MessageInstance#deliveryCount
differently to the AMQP 1.0 protocol layer.    This will need some care to ensure that protocol's
play nicely together.
> Also verify:
> * Behaviour when the session is rolled back or the recovered.
> * Behaviour when the session or connection is closed.
> * Behaviour when the connection is abruptly dropped.



--
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