Bug 978279 - Message.setJMSMessageID() error message is incorrect
Message.setJMSMessageID() error message is incorrect
Status: NEW
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-java (Show other bugs)
2.3
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: messaging-bugs
Michal Toth
:
Depends On: 978135
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-26 05:10 EDT by Michal Toth
Modified: 2015-11-15 20:18 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 978135
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michal Toth 2013-06-26 05:10:19 EDT
+++ This bug was initially created as a clone of Bug #978135 +++

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:
Comment 1 Michal Toth 2013-06-26 05:14:21 EDT
This bug is a follow up for BZ 952750

Note You need to log in before you can comment on or make changes to this bug.