Hi What JDK and OS are you using? And do you know how many cores your CPU has?
And can you put together a small app / unit test that triggers this issue on your system? On Mon, Jun 11, 2012 at 8:23 PM, jhart <james.h...@nokia.com> wrote: > Thanks. > > From: ext jhart [via Camel] [mailto: > ml-node+s465427n5714299...@n5.nabble.com] > Sent: Monday, June 11, 2012 2:22 PM > To: Hart James (Nokia-LC/Malvern) > Subject: Re: Possible threading issue > > 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); > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > > http://camel.465427.n5.nabble.com/Possible-threading-issue-tp5714069p5714299.html > To unsubscribe from Possible threading issue, click here< > http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5714069&code=amFtZXMuaGFydEBub2tpYS5jb218NTcxNDA2OXwtMTY1NDQ3ODE3NA== > >. > NAML< > http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > > > > ________________________________ > The information contained in this communication may be CONFIDENTIAL and is > intended only for the use of the recipient(s) named above. If you are not > the intended recipient, you are hereby notified that any dissemination, > distribution, or copying of this communication, or any of its contents, is > strictly prohibited. If you have received this communication in error, > please notify the sender and delete/destroy the original message and any > copy of it from your computer or paper files. > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Possible-threading-issue-tp5714069p5714300.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
