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] [Resolved] (QPIDJMS-85) ensure deliveries have state when settled during cleanup
Date Wed, 15 Jul 2015 15:07:04 GMT

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

Robbie Gemmell resolved QPIDJMS-85.
    Resolution: Fixed

> ensure deliveries have state when settled during cleanup
> --------------------------------------------------------
>                 Key: QPIDJMS-85
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-85
>             Project: Qpid JMS
>          Issue Type: Improvement
>          Components: qpid-jms-client
>    Affects Versions: 0.3.0
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>             Fix For: 0.4.0
> When clearing up link objects any unsettled deliveries get settled by Proton. It does
this without any delivery state if they have not previously been given any. While this is
perfectly legal protocol usage, it can be confusing and additionally relies on the other peer
doing the correct thing in that scenario. It would be ncier to set an explicit state, and
there are also cases (e.g client ack) where we might want the some of deliveries to have different
state than the default-outcome.
> Proton 0.10 adds support for specifying a 'default delivery state' to apply rather than
leaving the state unset when settling, we can use this to ensure deliveries get a fallback
state at settlement if not otherwise given one explicitly.

This message was sent by Atlassian JIRA

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

View raw message