ActiveMQ
  1. ActiveMQ
  2. AMQ-3006

STOMP connector assigns wrong default priority to incoming messages

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.4.1
    • Fix Version/s: 5.5.0
    • Component/s: Transport
    • Labels:
      None
    • Environment:

      Windows Vista

      Description

      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.

        Activity

        Hide
        Timothy Bish added a comment -

        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.

        Show
        Timothy Bish added a comment - 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.

          People

          • Assignee:
            Timothy Bish
            Reporter:
            Michael Justin
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development