You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Artur Kupiec (JIRA)" <ji...@apache.org> on 2015/10/28 10:50:28 UTC

[jira] [Comment Edited] (AMQ-4072) RESTful HTTP interface responses do not contain a correlation ID header

    [ https://issues.apache.org/jira/browse/AMQ-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978081#comment-14978081 ] 

Artur Kupiec edited comment on AMQ-4072 at 10/28/15 9:49 AM:
-------------------------------------------------------------

I checked version 5.12.1 and this problem seems to be unresolved. I also notice this bug concerns as well others default JMS mesasge properties (despite custom properties working well).

Thanks to comment [#comment-13462365]  added by [~steve.v] I was able to create simple patch fixing this problem.

I done my best to keep backward compatibility but You may like to reconsider changing old header names form destination to JMSDestinatnion and id to JMSMessageId


was (Author: artur.kupiec):
I checked version 5.12.1 and this problem seems to be unresolved. I also notice this bug concerns as well others default JMS mesasge properties (despite custom properties working well).

Thanks to comment [#comment-13462365]  added by [~steve.v] I was able to create simple patch fixing this problem.

> RESTful HTTP interface responses do not contain a correlation ID header
> -----------------------------------------------------------------------
>
>                 Key: AMQ-4072
>                 URL: https://issues.apache.org/jira/browse/AMQ-4072
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.6.0
>         Environment: RESTful HTTP client
>            Reporter: Stephen Vincent
>             Fix For: 5.x
>
>         Attachments: CorrelId.java, default_JMS_Message_Properties.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)