activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Closed: (AMQ-3172) Add support for Message Priority to Stomp
Date Mon, 07 Feb 2011 22:54:57 GMT


Timothy Bish closed AMQ-3172.

    Resolution: Not A Problem

Working as designed, the message will be in order if both are allow to get to the queue before
the consumer receive.

> Add support for Message Priority to Stomp
> -----------------------------------------
>                 Key: AMQ-3172
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Transport
>    Affects Versions: 5.4.2
>            Reporter: Craig Lewis
>            Priority: Minor
>         Attachments:
> Creating a Stomp message with a priority header has no effect.  The messages are delivered
in FIFO order, not priority order.
> The Stomp transport (activemq-core/src/main/java/org/apache/activemq/transport/stomp/
is calling msg.setJMSPriority(), but never calls producer.setPriority().  Because of this,
messages claims to have a priority, but the messages are never actually re-ordered.
> I believe a new unit test should be added to activemq-core/src/test/java/org/apache/activemq/transport/stomp/
 It should send 2 messages at different priorities, and verifies that they are re-ordered
by ActiveMQ.  I'll attach a unit test.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message