Description of problem: When Message.setJMSMessage is called with input "myString", the error message states: javax.jms.JMSException: MessageId 'myId' is not of the correct format, it must be ID: followed by a UUID at org.apache.qpid.client.message.AMQMessageDelegate_0_10.setJMSMessageID(AMQMessageDelegate_0_10.java:197) at org.apache.qpid.client.message.AbstractJMSMessage.setJMSMessageID(AbstractJMSMessage.java:63) ... In fact, the message must be "ID:<anyString>" The second part of the string can be any string, as of MRG-M 2.3.3 (see Bug 952750) Version-Release number of selected component (if applicable): qpid-java-0.18-8 (MRG-M 2.3.3) How reproducible: 100% Steps to Reproduce: 1. call setJMSMessageID() using any invalid string (such as one that does not start with "ID:") 2. 3. Actual results: Incorrect error message is generated Expected results: Message should be something like: MessageId 'myId' is not of the correct format, it must be of the form "ID:<anyString>" Additional info:
Posted a fix upstream at http://svn.apache.org/r1506068
Bug fix tested on both RHEL6 architectures. Error message works as expected. Tested using qpid-cpp-server-0.22-11.el6 qpid-java-client-0.22-5.el6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1296.html