Hi,
i have a route definition like:
from("file:/dir")
.split()
.tokenizeXML("element", "root").streaming()
.parallelProcessing().threads(10, 15)
.process(...)
.to("mock:out")
.end()
I assume that this would result in a XML splitting with up to 15 threads and
minimum 10 threads.
But logging in the process step tells me thread numbers up to 45?
The same thing happens if i am using a ThreadPoolProfile configured over a
Java Configuration class.
What is the problem with my route definition?
I am using Camel 2.17.1 and Spring 4.2.5. The route is in a single
RouteBuilder class loaded as @Component.
Best regards,
Zipunrar
--
View this message in context:
http://camel.465427.n5.nabble.com/Split-EIP-not-using-defined-thread-pool-size-tp5787075.html
Sent from the Camel - Users mailing list archive at Nabble.com.
