Hi,
You need to consider to upgrade the camel version to 2.9.x.
This issue should be fixed by CAMEL-4915[1]
[1]https://issues.apache.org/jira/browse/
CAMEL-4915
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://
We did this in one of our projects by providing a bean to the splitter
which returns an iterator. In this iterator, we first read the first line
and store it in this iterator as instance variable. For each next() call,
we read the next line and and "prefix" it with the first line.
Best,
Christian
Thanks, but are you sure end() is being used to end the route there? It's not
clear to me and I can't find any more documentation on end() anywhere. I saw
this other example and it doesn't look like it's being used to end the route
prematurely the way I'd like to. Note that in the XML version, ther
I tried to reproduce your issue with the following test - without look
(using Camel 2.10.2 and ActiveMQ 5.7.0):
- 10 parallel producer
- each will send 200 messages
- 5 consumers total
public class CamelJmsSharedFixReplyQueueTest extends CamelSpringTestSupport
{
private int senderCount = 10;