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 <pradeepnc...@gmail.com> 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 from a IBM mq.
> Ex: from("jms:// mq1?concurrentConsumers=10").log("").to("direct:test")
> Since the concurrentConsumers are 10 i believe the total threads used are
> 10.
>
> 2. The CPU has 2 cores
>
> We used a third party jaxp-ri-1.4.5.jar for parsing.
>
> Regards,
> Pradeep N
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/org-xml-sax-SAXException-FWK005-parse-may-not-be-called-while-parsing-tp5767851p5767859.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
