qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajith Attapattu (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Resolved: (QPID-427) Message ID not set properly (need to set a UUID)
Date Mon, 02 Apr 2007 17:39:32 GMT

     [ https://issues.apache.org/jira/browse/QPID-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rajith Attapattu resolved QPID-427.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: M2

This is fixed in the M2 branch at r523747.

The message id is set to a UUID.
However the MessageProducer.disableMessageID is checked before setting/generating the message
id.

If the above flag is true then the message id is set to null.

Rajith

> Message ID not set properly (need to set a UUID)
> ------------------------------------------------
>
>                 Key: QPID-427
>                 URL: https://issues.apache.org/jira/browse/QPID-427
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>            Reporter: Rajith Attapattu
>             Fix For: M2
>
>
> Currently if the message id is not set explicitly the client library uses the delivery
tag which is -1.
> We need to ensure that the client (message producer) sets the message id to UUID.
>  
> Regards,
> Rajith

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message