I have a wireTap in a route (route A) and the wireTap creates a new message
and is directed to a new route (route B).
A -> WT -> to(dest) |
\/
B
B -> to(jms:queue:output) -each thread in the pool with hang if the
jms queue is full
If B is publishing to a JMS Queue that fills up and blocks (as is the case
with Activemq by default) then it appears that after the thread pool that is
used by the wireTap is exhausted (due to jms hangs), then route A will hang.
I would think that you would want to bypass the wiretap at this point as it
is a liability and not impact route A.
So, how is the executor being called in a route with a wireTap and should
the wireTap be avoided when the wireTap thread pool is exhausted?
Thanks,
Bret
--
View this message in context:
http://camel.465427.n5.nabble.com/wireTaps-really-asynchronous-tp4648387p4648387.html
Sent from the Camel - Users mailing list archive at Nabble.com.
