Bug 978279 - Message.setJMSMessageID() error message is incorrect
Summary: Message.setJMSMessageID() error message is incorrect
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-java
Version: 2.3
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: Michal Toth
URL:
Whiteboard:
Depends On: 978135
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-26 09:10 UTC by Michal Toth
Modified: 2025-02-10 03:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 978135
Environment:
Last Closed: 2025-02-10 03:28:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michal Toth 2013-06-26 09:10:19 UTC
+++ 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 09:14:21 UTC
This bug is a follow up for BZ 952750

Comment 4 Red Hat Bugzilla 2025-02-10 03:28:02 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


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