activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Vincent (JIRA)" <>
Subject [jira] [Commented] (AMQ-4072) RESTful HTTP interface responses do not contain a correlation ID header
Date Tue, 25 Sep 2012 07:04:07 GMT


Stephen Vincent commented on AMQ-4072:

I just realized something else about that java test pgm I attached.  It was setting a string
property named correlationId as well as setting the correlation ID header field.  Specifically:

    message.setStringProperty( "correlationId", correlId );
    message.setJMSCorrelationID( correlId );

Since the MessageServlet's setResponseHeaders gets properties, that is why the HTTP response
contains a "correlationId" header.  If I comment-out the setting of the string property, and
only make the setJMSCorrelationID call, then the Java pgm does *not* receive a correlationId
header in the response.  That makes sense now.

While the fix for does enable the MessageServlet
to send message properties back by way of HTTP response headers.  It is not a fix for this
jira, which is asking for the JMSCorrelationID message header to be sent back in the response.
 I assume it should go back by way of a HTTP response header, but should take precedence over
a message property having the same name.
> RESTful HTTP interface responses do not contain a correlation ID header
> -----------------------------------------------------------------------
>                 Key: AMQ-4072
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.6.0
>         Environment: RESTful HTTP client
>            Reporter: Stephen Vincent
>            Priority: Critical
>             Fix For: 5.7.0
> When using a RESTful HTTP client to GET a message that has a correlation ID, the correlation
ID is not sent as a header in the response from the broker.  This inhibits my RESTful HTTP
client from performing request-response.

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:

View raw message