Back to bug 705015

Who When What Removed Added
Siddhesh Poyarekar 2011-05-16 12:17:41 UTC Priority unspecified medium
Group devel
Rajith Attapattu 2011-05-16 19:38:31 UTC Status NEW ASSIGNED
CC rattapat
Assignee rhm-maint-list rattapat
ranjith ruban 2012-11-05 06:58:45 UTC CC rruban
Pavel Moravec 2012-11-05 16:47:00 UTC Group private
CC pmoravec
Hardware Unspecified All
Version 1.3 2.2
OS Unspecified Linux
Pavel Moravec 2012-11-05 16:47:22 UTC Link ID Apache JIRA QPID-3272
Stuart Auchterlonie 2012-11-06 15:00:03 UTC CC sauchter
Justin Ross 2012-12-04 20:25:34 UTC Priority medium high
CC jross
Target Milestone --- 2.4
J.H.M. Dassen (Ray) 2012-12-17 11:23:44 UTC CC rdassen
Blocks 785156
Rajith Attapattu 2013-02-04 21:15:44 UTC Status ASSIGNED POST
Zdenek Kraus 2013-02-26 13:52:21 UTC CC zkraus
Zdenek Kraus 2013-02-26 14:42:28 UTC Flags needinfo?(rattapat)
Leonid Zhaldybin 2013-03-05 12:53:06 UTC CC lzhaldyb
Rajith Attapattu 2013-03-07 19:59:03 UTC Doc Text Cause:
The message implementation doesn't allow a non UUID string to be set as the message ID.

Consequence:
When a Qpid jms message is to be sent via a 3rd party message provider setting the message-id throws an exception if it was not a valid UUID.

Fix:
Allow any String to be set as the message ID. However when sending the message throw the Qpid JMS producer we set it to a UUID (as per the JMS spec and AMQP spec).

Result:
You can now set any String as the message ID when sending a Qpid JMS message through a 3rd party sender.
Flags needinfo?(rattapat)
Zdenek Kraus 2013-03-08 05:12:17 UTC Flags needinfo?(rattapat)
Mike Cressman 2013-04-16 15:33:41 UTC Blocks 952750
Valiantsina Hubeika 2013-04-19 13:53:34 UTC CC mtoth, vhubeika
Rajith Attapattu 2013-04-25 14:03:26 UTC Flags needinfo?(rattapat)
Mike Cressman 2013-04-25 14:14:24 UTC CC hchirino, mcressma
Michal Toth 2013-05-21 08:00:36 UTC QA Contact mrgqe-bugs mtoth
Justin Ross 2013-05-21 20:31:59 UTC Fixed In Version 0.22
Irina Boverman 2013-05-31 17:30:15 UTC Status POST MODIFIED
Fixed In Version 0.22 qpid-java-0.22-1.el5, qpid-java-0.22-2.el6
Michal Toth 2013-06-20 09:39:13 UTC Status MODIFIED ON_QA
Michal Toth 2013-06-20 13:14:25 UTC Status ON_QA VERIFIED
Simon Green 2013-07-02 00:11:28 UTC CC rruban rpiddapa
Simon Green 2013-07-03 04:42:24 UTC CC rdassen rbinkhor
Eric Sammons 2013-07-10 13:32:49 UTC Target Milestone 2.4 3.0
Justin Ross 2013-09-19 18:17:24 UTC Status VERIFIED ASSIGNED
Justin Ross 2013-09-30 12:55:03 UTC Status ASSIGNED MODIFIED
Fixed In Version qpid-java-0.22-1.el5, qpid-java-0.22-2.el6 qpid-java-0.22-1.el5, qpid-java-0.22-2.el6, qpid-java-0.23-1
Justin Ross 2013-09-30 12:55:57 UTC Flags needinfo?(rattapat)
errata-xmlrpc 2013-10-03 13:59:17 UTC Status MODIFIED ON_QA
Justin Ross 2013-11-08 19:26:40 UTC Status ON_QA VERIFIED
Fixed In Version qpid-java-0.22-1.el5, qpid-java-0.22-2.el6, qpid-java-0.23-1 qpid-java-0.22-1.el5, qpid-java-0.22-2.el6
Rajith Attapattu 2014-02-10 14:46:48 UTC Flags needinfo?(rattapat)
Leonid Zhaldybin 2014-09-22 09:25:57 UTC Group private, devel
Jared MORGAN 2014-09-23 00:45:52 UTC Doc Text Cause:
The message implementation doesn't allow a non UUID string to be set as the message ID.

Consequence:
When a Qpid jms message is to be sent via a 3rd party message provider, setting the message-id throws an exception if it was not a valid UUID.

Fix:
Allow any String to be set as the message ID. However when sending the message throw the Qpid JMS producer we set it to a UUID (as per the JMS spec and AMQP spec).

Result:
You can now set any String as the message ID when sending a Qpid JMS message through a 3rd party sender.
It was discovered that the message implementation did not allow a non-UUID string to be set as the message ID. When a Qpid JMS message was sent through a third-party message provider, setting the message-id resulted in an exception if the message-id was not a valid UUID. The fix now allows any string to be set as the message ID. When sending the message through the Qpid JMS producer, it is set as a UUID (as per the JMS spec and AMQP spec).
errata-xmlrpc 2014-09-24 15:02:50 UTC Status VERIFIED CLOSED
Resolution --- ERRATA
Last Closed 2014-09-24 11:02:50 UTC
John Skeoch 2015-09-14 00:22:36 UTC CC mnewsome

Back to bug 705015