CODEWITHSUNDEEP
javaapache-camel
jeff porter
jeff porter

Reputation: 6620

Camel SEDA and VM endpoints not uses all threads

I have the following route...

<route id="VM01_spit_products">
    <from uri="direct:processXML" />
    <split>
        <method ref="CamelSplitOnKey" method="splitIntoBatches" /> 
        <to uri="vm:processXMLSplit" />
    </split>
</route>

<route id="VM01_processXML">
    <from uri="vm:processXMLSplit?concurrentConsumers=15" />
    <bean ref="Builder" method="createXMLFile" />
    <to uri="{{ChangeReceiver}}" />
</route>

I was expecting with the use of VM or SEDA to mean that if the spliter is producing 5 messages, then one of the 15 threads I have defined would pick up each of these messages. When I debug into the Builder class, I can see that the messages are being picked up sequentially.

I see the same if I an using VM or SEDA.

Can someone suggest where I'm going wrong?

Notes:

New info.

I've added this code into my Builder.java

SedaEndpoint seda = (SedaEndpoint) camelContext.getEndpoint("seda:processXMLSplit");
int size = seda.getExchanges().size();
System.out.println("size ["+size+"]");

This prints a size of 0 each time.

This makes me think that the split isn't queuing up the messages as I expect.

Upvotes: 2

Views: 540

Answers (1)

jnupponen
jnupponen

Reputation: 745

Even if you have defined your vm consumer to have 15 threads it doesn't affect how your Split is working. By default Split is working sequentially so you must configure your Split to use parallelProcessing in order to get the result you want. See further in Splitter ParallelProcessing. Note also @Itsallas comment that you might need your vm endpoint configured with the same parameters.

Upvotes: 1

Related Questions