Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 77613 invoked from network); 24 Apr 2009 12:34:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Apr 2009 12:34:27 -0000 Received: (qmail 33720 invoked by uid 500); 24 Apr 2009 12:34:27 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 33675 invoked by uid 500); 24 Apr 2009 12:34:27 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 33665 invoked by uid 99); 24 Apr 2009 12:34:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2009 12:34:27 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2009 12:34:17 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LxKbM-0004zk-Vj for users@camel.apache.org; Fri, 24 Apr 2009 05:33:56 -0700 Message-ID: <23215582.post@talk.nabble.com> Date: Fri, 24 Apr 2009 05:33:56 -0700 (PDT) From: "raulvk.soa" To: users@camel.apache.org Subject: Re: Concurrency Issue with camel-validation In-Reply-To: <5380c69c0904240348ycacbdb0pe7752d21c3a5edd9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: raulvk.soa@gmail.com References: <23213294.post@talk.nabble.com> <5380c69c0904240348ycacbdb0pe7752d21c3a5edd9@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi Claus, Ticket created: https://issues.apache.org/activemq/browse/CAMEL-1565. Any ideas on a temporary workaround while the fix is found? Many thanks! Claus Ibsen-2 wrote: >=20 > Hi >=20 > Could you create a ticket in JIRA for this. >=20 > Link to jira from here: > http://camel.apache.org/support.html >=20 > Then we wont forget and will be able to put in a fix >=20 > On Fri, Apr 24, 2009 at 11:53 AM, raulvk.soa wrote= : >> >> Hi, >> >> I have a Camel flow which seems to be experimenting concurrency issues >> with >> the camel-validation component. This flow is invoked twice in parallel b= y >> a >> splitter. >> >> It seems like the camel-validation component lazily-loads the XSD, when >> the >> first request comes in. >> As a consequence, when two simultaneous requests are received, it >> attempts >> to load the XSD twice at the same time, possibly using the same >> SchemaFactory, which may not be thread-safe. >> >> Any ideas on how to tell Camel to load the XSD on initialization of the >> flow, instead of on the first request? >> >> Many thanks! >> >> --------------------------- >> >> Dump of the stack trace: >> >> 10:38:20,860 | ERROR - org.apache.camel.processor.DeadLetterChannel - >> org.apache.camel.processor.Logger - Failed delivery for exchangeId: >> ID-ATOS-B624 >> E47AF0/3211-1240562892751/0-11. On delivery attempt: 0 caught: >> org.xml.sax.SAXException: FWK005 parse may not be called while parsing. >> org.xml.sax.SAXException: FWK005 parse may not be called while parsing. >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> com.sun.org.apache.xerces.internal.jaxp.validation.Util.toSAXException(U= til.java:62) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> com.sun.org.apache.xerces.internal.jaxp.validation.XMLSchemaFactory.newS= chema(XMLSchemaFactory.java:214) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:594) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> org.apache.camel.processor.validation.ValidatingProcessor.createSchema(V= alidatingProcessor.java:204) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> org.apache.camel.processor.validation.ValidatingProcessor.getSchema(Vali= datingProcessor.java:118) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> org.apache.camel.processor.validation.ValidatingProcessor.process(Valida= tingProcessor.java:54) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.jav= a:92) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java= :66) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> org.apache.camel.impl.converter.AsyncProcessorTypeConverter$ProcessorToA= syncProcessorBridge.process(AsyncProcessorTypeConverter.java:43) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:75) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> org.apache.camel.management.InstrumentationProcessor.process(Instrumenta= tionProcessor.java:57) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.j= ava:155) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.j= ava:91) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at org.apache.camel.processor.Pipeline.proces= s(Pipeline.java:101) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at org.apache.camel.processor.Pipeline.proces= s(Pipeline.java:85) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >> org.apache.camel.management.InstrumentationProcessor.process(Instrumenta= tionProcessor.java:57) >> -- >> View this message in context: >> http://www.nabble.com/Concurrency-Issue-with-camel-validation-tp23213294= p23213294.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> >> >=20 >=20 >=20 > --=20 > Claus Ibsen > Apache Camel Committer >=20 > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > Apache Camel Reference Card: > http://refcardz.dzone.com/refcardz/enterprise-integration >=20 >=20 --=20 View this message in context: http://www.nabble.com/Concurrency-Issue-with-= camel-validation-tp23213294p23215582.html Sent from the Camel - Users mailing list archive at Nabble.com.