[
https://issues.apache.org/jira/browse/AMQ-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3006.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.5.0
Assignee: Timothy Bish
Applied fix in trunk to properly set default priority if one isn't set on the
message.
Created a test to ensure it stays fixed.
> STOMP connector assigns wrong default priority to incoming messages
> -------------------------------------------------------------------
>
> Key: AMQ-3006
> URL: https://issues.apache.org/jira/browse/AMQ-3006
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.4.1
> Environment: Windows Vista
> Reporter: Michael Justin
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.5.0
>
>
> If a client sends a Stomp frame without a priority header, the broker does
> not set the message priority to the default value (4) which is specified in
> the JMS spec (see
> http://download.oracle.com/javaee/1.4/api/javax/jms/Message.html:
> DEFAULT_PRIORITY The message producer's default priority is 4.)
> As effect, the message will have priority 0 (lowest).
> Adding a priority header for all messages by the Stomp client, even for
> default priority, would also cause larger messages to be sent over the wire.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
