[jira] [Work logged] (CAMEL-13750) Incoming JMSCorrelationID is passed along when useMessageIDAsCorrelationID

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-13750?focusedWorklogId=279000&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-279000 ]

ASF GitHub Bot logged work on CAMEL-13750:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Jul/19 13:58
            Start Date: 18/Jul/19 13:58
    Worklog Time Spent: 10m 
      Work Description: alvinkwekel commented on pull request #3049: CAMEL-13750: Omit JMSCorrelationID when sending with useMessageIDAsCo…
URL: https://github.com/apache/camel/pull/3049
 
 
   When the setting useMessageIdAsCorrelationid is true for the client and false for the server and a correlation id is set on the message then we expect the client to omit the correlation id on the JMS message to force the server to use the message id. But the correlation id should still be available on the client exchange message afterwards.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 279000)
            Time Spent: 10m
    Remaining Estimate: 0h

> Incoming JMSCorrelationID is passed along when useMessageIDAsCorrelationID
> --------------------------------------------------------------------------
>
>                 Key: CAMEL-13750
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13750
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-activemq, camel-jms
>    Affects Versions: 2.24.1
>            Reporter: Alvin Kwekel
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
>  
> {noformat}
> +-+            +-+            +-+
> | | +-> Q1 +-> | | +-> Q3 +-> | |
> |A|            |B|            |C|
> | | <-+ Q2 <-+ | | <-+ Q4 <-+ | |
> +-+            +-+            +-+{noformat}
>  JMS request goes from A to B to C and the reply back from C to B to A.
> A useMessageIDAsCorrelationID=false
>  B useMessageIDAsCorrelationID=true
>  C useMessageIDAsCorrelationID=false
> The JMSCorrelationID assigned by A is passed along to C via Camel message headers when useMessageIDAsCorrelationID is set on B's request. B is expecting the JMSMessageID to be used as JMSCorrelationID on the reply but since the JMSCorrelationID is actually provided, C could decide to give precedence to the JMSCorrelationID rendering B's message selector to not match.
> The only case this would work as expected is when C is also set to useMessageIDAsCorrelationID to always prefer the JMSMessageID. But consider situations where C is not under your control and/or implemented in a different technology than Camel.
> I'd argue the JMSCorrelationID should be made _null_ when the useMessageIDAsCorrelationID is set on a provider.
> I've created an example project to demonstrate the behavior: [https://github.com/alvinkwekel/camel-example-jmscorrelationid]
> This issue seems to be closely related to https://issues.apache.org/jira/browse/CAMEL-2249



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)