[
https://issues.apache.org/activemq/browse/CAMEL-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43760#action_43760
]
Marat Bedretdinov commented on CAMEL-642:
-----------------------------------------
I'm a little bit surprised how this test could have worked at all...
Looking at the route that this test is testing:
from("jms:queue:reply").aggregator(header("cheese").....
and then debugging through it show that this portion of the route
'from("jms:queue:reply)' creates an event driven JMS consumer, and then the
'aggregator' bit creates a JMS polling consumer on the *same* destination.
This is clearly a race, as we now have two consumers competing for messages off
the same destination.
It seems a possible fix for this type of construct would be having the 'from'
type realize that its followed by an aggregator and then disable creation of
its even driven consumer and letting the aggregator get the messages and then
deliver them to their ultimate destinations
Comments?
> jms aggregation does not work
> -----------------------------
>
> Key: CAMEL-642
> URL: https://issues.apache.org/activemq/browse/CAMEL-642
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-jms
> Reporter: Willem Jiang
>
> I found this issue when I test Camel 1.4.0 RC2 kit, I just add a test case
> to show the error.
> https://svn.apache.org/repos/asf/activemq/camel/trunk/components/camel-jms/src/test/java/org/apache/camel/component/jms/AggregratedJmsRouteTest.java
> You can reproduce the error if you remove the x character from
> xtestJmsMulticastAndAggregration() method.
> BTW the test case works with the Camel 1.4.0 RC1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
