[OASIS Issue Tracker] (AMQPBINDMAP-18) Document handling of out-of-range message priority

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/AMQPBINDMAP-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Godfrey updated AMQPBINDMAP-18:
-----------------------------------

    Priority: Blocker  (was: Minor)

> Document handling of out-of-range message priority
> --------------------------------------------------
>
>                 Key: AMQPBINDMAP-18
>                 URL: https://issues.oasis-open.org/browse/AMQPBINDMAP-18
>             Project: OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC
>          Issue Type: Bug
>          Components: JMS Mapping
>    Affects Versions: wd06
>            Reporter: Steve Huston
>            Assignee: Robert Gemmell
>            Priority: Blocker
>
> JMSPriority and AMQP priority ranges are not the same (JMS wd states this). The spec should state the desired behavior when a JMS client receives a message with out-of-range priority.
> Note that currently the Qpid JMS client scales the receives AMQP priority value into the valid JMS range. However, there is now ay to set or find out the original value.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)