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 Wed, 26 Sep 2012 16:51:07 GMT


Stephen Vincent commented on AMQ-4072:

   I would like that, but finding the time will be difficult.  I am currently under the gun
with respect to some deadlines, so can't be anytime soon.  

   With respect to the needs of my client app, I should mention it is a C-based client.  In
the past, I already developed C-based interfaces that hop over through JNI to a JVM where
I load a JMS provider.  However, now I am developing C-based interfaces that avoid a client-side
JVM.  If I understand things, my two top choices are to access the ActiveMQ broker RESTfully
over HTTP, or develop a C-wrapper to the ActiveMQ-CPP client library.  The latter seems involved
and includes dependencies on open source client libraries such as ActiveMQ-CPP and the APR.
 Given that someone else in my organization has already developed some C-based HTTP interfaces,
I thought it would be best to choose the former, and make use of the HTTP protocol.

   The C-based HTTP client code I call, establishes a connection using a URL.  Once connected,
I can make many POST and GET requests, but I am encountering problems with respect to correlation
ID's.  I cannot change the URL unless I re-connect, and I don't want to do that.  So, the
only way I have found to POST messages within the same session/connection and with varying
correlation ID's, is to use a content-type of "application/x-www-form-urlencoded".  That is
a bit restrictive because then my users have to make sure the data is formatted correctly.
 For example, you can't just send any text, without having to worry about special characters
such as ampersand("&").  Also, the only way I have found to obtain the correlation ID
when GETting a message, is when the correlation ID was actually put in the message as a string
property, and I must know the name of the property.  Making use of the JMSCorrelationID header
field would be ideal, but the current MessageServlet doesn't support it with respect to the
pattern I mention above.

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