27;t help too. Also I've noticed that thread is becoming
unavailable after the timeout specified for the calls has been reached.
Although not every timeout leads to a thread leak.
Can you suggest what else can be checked? Am I missing something? Or may be
this is a bug in Camel?
--
Al
situation didn't change much. NettyOrderedWorker
threads are still getting stuck in a WAITING state after some time
following the start of an app as well as RecipientList threads.
What else can be checked? I can provide additional info if needed.
On Mon, Apr 20, 2015 at 4:19 PM, Alexander I
