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

Martin Lichtin edited comment on AMQ-4921 at 12/6/13 9:08 AM:
--------------------------------------------------------------

I don't have an isolated unit test, but debugging it further reveals that Camel 
does this with the header I set:

JmsProducer                      | amel.component.jms.JmsProducer$2  315 | 126 
- org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination name 
topic://jmsqueuemonitor -> jmsqueuemonitor
JmsProducer                      | amel.component.jms.JmsProducer$2  315 | 126 
- org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination name 
topic://jmsqueuemonitor -> jmsqueuemonitor
JmsProducer                      | amel.component.jms.JmsProducer$2  331 | 126 
- org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue: 
jmsqueuemonitor
JmsProducer                      | amel.component.jms.JmsProducer$2  331 | 126 
- org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue: 
jmsqueuemonitor
JmsProducer                      | amel.component.jms.JmsProducer$2  343 | 126 
- org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination: 
queue://jmsqueuemonitor
JmsProducer                      | amel.component.jms.JmsProducer$2  343 | 126 
- org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination: 
queue://jmsqueuemonitor

I'd expect Camel to leave JMS headers as they are...



was (Author: lichtin):
I don't have an isolated unit test, but debugging it further reveals that Camel 
does this with the header I set:

| JmsProducer                      | amel.component.jms.JmsProducer$2  315 | 
126 - org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination 
name topic://jmsqueuemonitor -> jmsqueuemonitor
| JmsProducer                      | amel.component.jms.JmsProducer$2  315 | 
126 - org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination 
name topic://jmsqueuemonitor -> jmsqueuemonitor
| JmsProducer                      | amel.component.jms.JmsProducer$2  331 | 
126 - org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue: 
jmsqueuemonitor
| JmsProducer                      | amel.component.jms.JmsProducer$2  331 | 
126 - org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue: 
jmsqueuemonitor
| JmsProducer                      | amel.component.jms.JmsProducer$2  343 | 
126 - org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination: 
queue://jmsqueuemonitor
| JmsProducer                      | amel.component.jms.JmsProducer$2  343 | 
126 - org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination: 
queue://jmsqueuemonitor

I'd expect Camel to leave JMS headers as they are...


> Setting JMSReplyTo with a topic destination does not work
> ---------------------------------------------------------
>
>                 Key: AMQ-4921
>                 URL: https://issues.apache.org/jira/browse/AMQ-4921
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.7.0
>            Reporter: Martin Lichtin
>
> The use case is about communicating with the StatisticsPlugin:
> Sending a message and setting JMSReplyTo with a destination for the response 
> message(s).
> Doing (via Camel)
>       in.setHeader("JMSReplyTo", "topic://mydest");
> results in the broker producing messages to the "mydest" queue.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to