activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Genender (JIRA)" <>
Subject [jira] [Commented] (AMQ-5903) Message headers are lost when using the Broker Component for Camel
Date Thu, 30 Jul 2015 00:36:04 GMT


Jeff Genender commented on AMQ-5903:

and Paul Gale ;-)

> Message headers are lost when using the Broker Component for Camel
> ------------------------------------------------------------------
>                 Key: AMQ-5903
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-camel
>    Affects Versions: 5.11.1
>            Reporter: Heath Kesler
>             Fix For: 5.12.0
>         Attachments: amq-5903.patch
> When using the broker camel component as defined here:
> There appears to be an undocumented limitation of the broker component's current implementation.
I need to know whether said limitation is by design or an oversight. If it's an oversight
then I can submit a patch for it.
> This example route does not work as expected - the JMSXGroupID header is lost when received
by the broker component.
> <route> 
> <from uri="broker:queue:test"/> 
> <setHeader headerName="JMSXGroupID"> 
> <constant>123</constant> 
> </setHeader> 
> <to uri="broker:queue:test"/> 
> </route>
> After single stepping with a debugger the component executes this code:
> As you can see from the method's implementation it only copies over a fixed set of six
well-known headers. All other headers on the inbound message are discarded. Why not copy over
every header? Consequently the JMSXGroupID header is not copied, despite being present on
the inbound message.
> This would appear to be a bug in my opinion as I do not believe we should be loosing
any headers on a message in this case.  

This message was sent by Atlassian JIRA

View raw message