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 02:58:09 GMT


Stephen Vincent commented on AMQ-4072:

I had an ugly mistake in the Java test program I attached.  The reason that test didn't show
me the correlation ID, is because due to an accidentally placed post increment, the loop prints
every other header.  Once I correct the test program, I do see it sending back a correlationId
when using that Java test.  For example:
Set-Cookie: JSESSIONID=1b82fgs19r3ay7k9hzklej070;Path=/demo
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Type: text/plain;charset=ISO-8859-1
destination: queue://myqueue
id: ID:d22275-4049-1348541259944-1:1:1:1:1
correlationId: Resty 123
Transfer-Encoding: chunked
Server: Jetty(7.6.7.v20120910)
HTTP/1.1 200 OK

However, that test pgm calls "resonse.getAllHeaders()".  I am puzzled about the header -vs-
property thing I read, and I don't understand why my C-based client is getting all but the
correlationId.  I guess "resonse.getAllHeaders()" is doing more than my C-based client.

> 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
>         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