org.xml.sax.SAXException: FWK005 parse may not be called while parsing.

2015-06-03 Thread pradeep
org.apache.camel.builder.xml.XPathBuilder.doInEvaluateAs(XPathBuilder.java:890) ~[camel-core-2.13.1.jar:2.13.1] ... 32 common frames omitted Caused by: org.xml.sax.SAXException: FWK005 parse may not be called while parsing. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:307) ~[jaxp-ri-1.4.5

Re: org.xml.sax.SAXException: FWK005 parse may not be called while parsing.

2015-06-04 Thread Claus Ibsen
va:615) > [na:1.7.0_71] > at java.lang.Thread.run(Thread.java:745) [na:1.7.0_71] > Caused by: javax.xml.xpath.XPathExpressionException: null > at > com.sun.org.apache.xpath.internal.jaxp.XPathExpressionImpl.evaluate(XPathExp

Re: org.xml.sax.SAXException: FWK005 parse may not be called while parsing.

2015-06-04 Thread pradeep
Hi Claus, Thank you for your reply. Here is my answers: 1. The above mentioned route consumes the message from other route, which consumes the messages from a IBM mq. Ex: from("jms:// mq1?concurrentConsumers=10").log("").to("direct:test") Since the concurrentConsumers are 10 i believe the total

Re: org.xml.sax.SAXException: FWK005 parse may not be called while parsing.

2015-06-04 Thread pradeep
Hi Claus, One more correction we are using direct-vm component instead of direct component in the below mentioned camel routes. . -- View this message in context: http://camel.465427.n5.nabble.com/org-xml-sax-SAXException-FWK005-parse-may-not-be-called-while-parsing-tp5767851p5767860.html Sen

Re: org.xml.sax.SAXException: FWK005 parse may not be called while parsing.

2015-06-04 Thread Claus Ibsen
Hi Try without your custom jaxp parser - it could be that guy that has a problem On Thu, Jun 4, 2015 at 11:21 AM, pradeep wrote: > Hi Claus, > > Thank you for your reply. Here is my answers: > > 1. The above mentioned route consumes the message from other route, which > consumes the messages fro