[
https://issues.apache.org/jira/browse/CAMEL-21656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17927819#comment-17927819
]
Raymond commented on CAMEL-21656:
---------------------------------
I upgraded to Camel 4.10.0 and ran the example again. Here are my findings that
may be interesting:
1. disableReplyTo
When adding explicitly the disableReplyTo as mentioned:
<to
uri="activemq6:log?exchangePattern=InOnly&disableReplyTo=true&timeToLive=86400000"/>
The route returns the expected response "b". Without modification it still
returns "a".
I still find this a bit odd as this apparently wasn't the old behavior and when
the exchangePattern is already set before to "InOnly" I wouldn't expect data
after setting that pattern.
2. Different results on the second call
I have a similar case with three CamelContext files from a customer (originally
created for Camel 2.23.x) and then update and run these with 4.10.0 then the
result is "Recipient 2.2" on the first call (which is the expected result), but
the subsequent calls return "Recipient 1.1".
> camel-jms - Multiple routes with direct/activemq and recipientlist returns
> unexpected result
> --------------------------------------------------------------------------------------------
>
> Key: CAMEL-21656
> URL: https://issues.apache.org/jira/browse/CAMEL-21656
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 4.9.0
> Reporter: Raymond
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.8.4, 4.10.0
>
> Attachments: first_integration-1.xml, first_integration.xml,
> main-xml2.zip, second_integration-1.xml, second_integration.xml,
> third_integration-1.xml, third_integration.xml
>
>
> I have a customer that upgraded from an old Camel version (2.23) to 4.9.0
> where the Camel 4 route returned an unexpected result. It's a bit of an
> edge/curious case.
> It was part of a bigger route, but I tried to create a minimal example to
> reproduce the issue.
> The following routes:
> {code:java}
> <routes>
> <route id="1">
> <from uri="jetty-nossl:http://0.0.0.0:9000/test"/>
> <step id="1">
> <to uri="activemq:2"/>
> </step>
> </route>
> <route id="2">
> <from uri="activemq:2"/>
> <step id="2">
> <to uri="direct:3"/>
> <to uri="activemq:log?exchangePattern=InOnly&timeToLive=86400000"/>
> </step>
> </route>
> <route id="3">
> <from uri="direct:3"/>
> <step id="3">
> <multicast>
> <to uri="direct:4a?exchangePattern=InOut"/>
> <to uri="direct:4b?exchangePattern=InOut"/>
> </multicast>
> </step>
> </route>
> <route id="4a">
> <from uri="direct:4a"/>
> <step id="4a">
> <setBody>
> <constant>a</constant>
> </setBody>
> <to
> uri="activemq:log?exchangePattern=InOnly&timeToLive=86400000"/>
> </step>
> </route>
> <route id="4b">
> <from uri="direct:4b"/>
> <step id="4b">
> <setBody>
> <constant>b</constant>
> </setBody>
> </step>
> </route>
> <route id="log">
> <from uri="activemq:log"/>
> <step id="log">
> <to uri="log:mylog"/>
> </step>
> </route>
> </routes> {code}
> returns the result: a
> expected result: b
> The expected result can be shown by changing small things in the route. For
> example:
> 1. Change the endpoint "activemq:2" to "direct:2"
> 2. Remove this line from route 2:
> <to uri="activemq:log?exchangePattern=InOnly&timeToLive=86400000"/>
> 3. Remove one of the parameters in route 4a of this line:
> <to uri="activemq:log?exchangePattern=InOnly&timeToLive=86400000"/>
> For example, just by removing the timeToLive option returns the expected
> result.
> ----------------------------
> With all of these small changes, the expected result 'b' returns. Can you
> check why this particular combination produces the unexpected result?
> Note: I used ActiveMQ 6.1.5 for testing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
