Red Hat Bugzilla – Bug 509395
The JMS Client does not default to the correct priority as specified in the spec
Last modified: 2010-10-14 12:15:56 EDT
Description of problem: The JMS Client does not default to the correct priority as specified in the spec. Currently it defaults to 0, but should be 4 Version-Release number of selected component (if applicable): 1.1.x How reproducible: Always Steps to Reproduce: Send a message as follows TextMessage txtMsg = session.createTextMessage(); prod.send(txtMsg); Actual results: If you print the message on the receiving side it you could see the priority as zero Expected results: It should be 4.
A fixed has been committed to rev 817478 on qpid trunk. I have also added a simple check for the default message priority in an existing test in JMSPropertiesTest.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: The JMS Client does not default to the correct priority as specified in the spec. Consequence: This does not really have any effect as the C++ broker does not yet support priority. Fix: The client now defaults to the correct priority (4). Result: When the C++ broker implements priority, the messages sent through the JMS client will be handled according to the JMS spec.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,7 +1 @@ -Cause: The JMS Client does not default to the correct priority as specified in the spec. +The JMS Client did not default to the correct priority as specified in the specification (0). This did not have any effect as the C++ broker does not yet support priority.With this update, the client now defaults to the correct priority (4). When the C++ broker implements priority, the messages sent through the JMS client will be handled according to the JMS specification.- -Consequence: This does not really have any effect as the C++ broker does not yet support priority. - -Fix: The client now defaults to the correct priority (4). - -Result: When the C++ broker implements priority, the messages sent through the JMS client will be handled according to the JMS spec.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0773.html