You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2011/02/07 23:54:57 UTC
[jira] Closed: (AMQ-3172) Add support for Message Priority to Stomp
[ https://issues.apache.org/jira/browse/AMQ-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: https://issues.apache.org/jira/browse/AMQ-3172
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Transport
> Affects Versions: 5.4.2
> Reporter: Craig Lewis
> Priority: Minor
> Attachments: StompTest.java.patch
>
>
> 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/FrameTranslator.java) 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/StompTest.java. 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: http://www.atlassian.com/software/jira