Stomp default message priority 0 instead of 4

[mjustin]

In tests of two message brokers (OpenMQ and HornetQ) I found a small difference in the Stomp transport implementations

* when a Stomp frame is sent to HornetQ which does not have a priority header line, the message receiver will see priority 0 (=lowest)

* with Open Message Queue (OpenMQ), the message receiver will see priority = 4

Maybe the OpenMQ behavior can be explained with the JMS spec which says that the default priority for message producers is 4: http://download.oracle.com/javaee/1.4/api/javax/jms/Message.html

Should the HornetQ Stomp acceptor also 'promote' frames which have no priority set to priority 4?

If not, I would modify my Stomp clients to add the priority header onyl if the value does not equal 0.

Michael

[clebert.suconic]

Well, Stomp is not really JMS.. you don't need have a spec mandating it...

however, I don't see a big deal on using messaging priority = 4. (probably a 2 lines/5 minutes change).

Feel free to open a JIRA, and i will take care of it before next release.

[mjustin]

I have created https://jira.jboss.org/browse/HORNETQ-560 now

(I have also submitted this suggestion to the Stomp 1.1 working group yesterday and received positive feedback already)

Michael

[clebert.suconic]

Do you have a link for the thread on google groups for the discussion? It would be nice to have a link here.

[mjustin]

Sure, I have also added it as a comment to the Jira entry:

The Stomp 1.1 working group URL is http://groups.google.com/group/stomp-spec , my post suggesting the new default is here http://groups.google.com/group/stomp-spec/browse_thread/thread/d9298591a728bb38

The Stomp 1.1 draft maintained by group members is at http://github.com/stomp/stomp-spec/blob/master/src/stomp-specification-1.1.md

[clebert.suconic]

what I was asking is if you had a link to the thread you were talking about this. I know where's the stomp working group... I was just wondering about the thread itself.