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, 21 May 2013 19:29:16 GMT


Stephen Vincent commented on AMQ-4072:

I know I talked about many things in this jira, but one of the outstanding issues is something
I think REST API client apps will find important -- having the response from a GET request
include the JMSCorrelationID in a response header.  Given that a JMS message's correlation
ID is actually a header field, not a property, the correlation ID is currently not accessible
to REST API clients that GET a message containing a correlation ID.  I consider correlation
IDs as an important feature, and it seems odd that REST API clients do not see correlation
IDs in the response to a GET request unless the producing application actually adds the correlation
ID as a message property instead of simply setting the correlation ID header field.

Another outstanding issue I mention in this jira, pertains to a REST API client app wanting
to change the selector within the scope of a session.  When the first GET request of a session
causes the broker to create a consumer on behalf of the client, it does honor the selector
header of that originating GET request.  However, subsequent GET requests within the session
that have a different selector header do not cause the broker to re-create the consumer using
the new selector.  That issue is important to me than the correlation ID issue.

I did not attach a test program to illustrate the selector issue, but the Java client test
program I attached to this jira can be used to illustrate the correllation ID issue.
> RESTful HTTP interface responses do not contain a correlation ID header
> -----------------------------------------------------------------------
>                 Key: AMQ-4072
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.6.0
>         Environment: RESTful HTTP client
>            Reporter: Stephen Vincent
>             Fix For: 5.x
>         Attachments:
> 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