Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Message-ID: <246660711.1208310703457.JavaMail.jira@brutus>
Date: Tue, 15 Apr 2008 18:51:43 -0700 (PDT)
From: "Marat Bedretdinov (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Created: (CAMEL-467) Implement ability to correlate
 request/reply message pairs over JMS using message ID as correlation ID
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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