[
https://issues.apache.org/activemq/browse/CAMEL-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea reassigned CAMEL-467:
-------------------------------------
Assignee: Hadrian Zbarcea
> Implement ability to correlate request/reply message pairs over JMS using
> message ID as correlation ID
> ------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-467
> URL: https://issues.apache.org/activemq/browse/CAMEL-467
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 1.4.0
> Reporter: Marat Bedretdinov
> Assignee: Hadrian Zbarcea
> Fix For: 1.4.0
>
> Attachments: camel-jms.2008.04.15-21.31.patch
>
>
> Unfortunately IBM MQ transforms user passed correlation ID to its own format,
> which makes using user generated correlation ID to correlate a call flow
> (request/reply, etc) impossible.
> The attached patch enables Camel to use JMS message ID as request/reply
> correlation ID without the need for a JMS Consumer with selector per request.
> This patch also address a small issue in cross brokers routing. In
> request/reply scenario, when request flows say from ActiveMQ into IBM MQ the
> ActiveMQ message gets a reply destination set on it that belongs to IBM MQ.
> This does not work. A configuration variable is introduced to force a message
> copy, which solves this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
