[jira] Resolved: (AMQ-3093) Client should provide handling of JMSPriority messages outside of range 0-9.

["Timothy Bish (JIRA)" <ji...@apache.org>]

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

Timothy Bish resolved AMQ-3093.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 5.5.0
         Assignee: Timothy Bish

Tested against trunk cannot reproduce.  Marked as fixed.

> Client should provide handling of JMSPriority messages outside of range 0-9.
> ----------------------------------------------------------------------------
>
>                 Key: AMQ-3093
>                 URL: https://issues.apache.org/jira/browse/AMQ-3093
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.4.2
>            Reporter: Robert Liguori
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 5.5.0
>
>         Attachments: JMSPriority.PNG
>
>
> The JMS spec states, "JMS defines a ten-level priority value, with 0 as the lowest priority and 9 as the
> highest. In addition, clients should consider priorities 0-4 as gradations of
> normal priority and priorities 5-9 as gradations of expedited priority."
> As such, you would assume that the client would abide by these rules and only set the priority between 0 and 9.
> The ActiveMQ web console allows for inputting any string.  It appears as if the client is looking for a value of type "byte" as it t transforms 128 into -128, and character strings to 0.
> I would recommend error handling for this condition by the client.  For example, if the value is over 9, set the value to 9, 4 (highest normal) or 0 (lowest priority).... whatever makes the most sense.... or don't process the message at all, as it's malformed (in a sense).
> Note: Really large integers appears to mess up the queue altogether.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira