You had 160 tps with a 100ms sleep that gives a pool of 16 threads. In Netty
4.0 the default pool size will be twice the number of cores, I guess it's the
same for current 3.x that camel is using. You are running on a system with 8
CPU cores (and 0% overhead inside netty or camel).
A computer c
A workaround is to use a SchemaFactory implementation that is thread safe. The
one bundled in JDK is not but the one in Xerces is.
On 2013-08-22, at 12:38, solimo wrote:
> Oh, how could I miss CAMEL-6630. Thanks.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com