[ 
https://issues.apache.org/jira/browse/AMQ-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

siva sankar closed AMQ-4939.
----------------------------

    Resolution: Invalid

> JMSXGroupID deleting from message headers in ActiveMQ
> -----------------------------------------------------
>
>                 Key: AMQ-4939
>                 URL: https://issues.apache.org/jira/browse/AMQ-4939
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.9.0
>         Environment: Production
>            Reporter: siva sankar
>
> Team,
> Version: activeMQ 5.9.0
> This recording is created on ActiveMQ regarding Message Grouping concept.
> we are trying to do message grouping based on string. We are adding 
> JMSXgroupID to the message headers (tried through camel and through a simple 
> client code). This JMSXGroupID getting missed/deleted when message placed in 
> activeMQ. We are guessing that activeMQ  deleting this header.
> Please see my camel code below.
> *****************CODE  
> START********************************************************
>       from(fromLocation)
>               .log("reading messages")
>                 .setHeader("JMSXGroupID",constant(100))
>                 .process(new Processor() {
>                       public void process(Exchange exchange) throws Exception 
> {
>   S.o. p("");
> }})
> process(new Processor() {
>                       public void process(Exchange exchange) throws Exception 
> {
>                               Message message = exchange.getIn();
>                               System.out.println(exchange.getIn().toString());
>                       }})
>               .to(endpoint);
> ********************CODE 
> END****************************************************
> endpoint configured as tcp://localhost:61616
> When i watch message through HermesJMS. JMSXGroupID was missed in headers.
> Please help on this.
> Thanks,
> Siva Sankar



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to