camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jhart <james.h...@nokia.com>
Subject Re: Possible threading issue
Date Mon, 11 Jun 2012 18:21:33 GMT
Thanks for the feedback, I've reviewed the references you pointed out and
decided to simplify the route.

I have remove all of my .threads(...) DSL calls.  I only use
parallelProcessing in 1 place now and I am still running into the problem.

Below is a version that fails and one that works because a threads(1,1)
makes it single threaded at 1 point.

*This route throws the NullPointerException:*

      ExpressionNode resultDefinition = routeDefinition.split()
              
.tokenizeXML(GenericTMCXMLProcessor.FLOW_TAG_DELIMITER).streaming()
               .parallelProcessing().timeout(timeout)
               .process(new GenericTMCXMLProcessor(appGlobals, jobProps))
               .split(genericTmcMappingProcessor)
               .process(preDestinationProcessor);
               .multicast()
                  .to(destinationURIs);

*This version works:*

      ExpressionNode resultDefinition = routeDefinition.split()
              
.tokenizeXML(GenericTMCXMLProcessor.FLOW_TAG_DELIMITER).streaming()
               .parallelProcessing().timeout(timeout)
               .process(new GenericTMCXMLProcessor(appGlobals, jobProps))
               .split(genericTmcMappingProcessor)
               .process(preDestinationProcessor);
               *.threads(1, 1)*
               .multicast()
                    .to(destinationURIs);


--
View this message in context: http://camel.465427.n5.nabble.com/Possible-threading-issue-tp5714069p5714299.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message