[
https://issues.apache.org/jira/browse/QPID-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491516#comment-13491516
]
Ted Ross commented on QPID-3272:
--------------------------------
A message id that is not in the form of a UUID can be unique. And conversely,
a message-id that is in the form of a UUID might not be unique.
I see from the source code that the message ID is of type UUID. Is this
strictly necessary? Is there a reason that it can't be a string?
IMO, the "UUID form" validation is too heavy-handed.
> Allow JMS messages originated from another vendor to be sent through Qpid
> with the Message ID intact.
> -----------------------------------------------------------------------------------------------------
>
> Key: QPID-3272
> URL: https://issues.apache.org/jira/browse/QPID-3272
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.6, 0.8, 0.10
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Priority: Minor
> Fix For: Future
>
>
> A message bridge it forwards messages between two different messaging
> providers.
> However when attempting to send a message from another vendor through Qpid,
> the send method throws an exception if the message ID is not a UUID.
> javax.jms.JMSException: MessageId
> 'ID:dhcp209-12.gsslab.pnq.redhat.com-45266-1305237148981-3:0:3:1:1' 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:165)
> at
> org.apache.qpid.client.message.AbstractJMSMessage.setJMSMessageID(AbstractJMSMessage.java:92)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
