David, Could you provide us with the code for the router bean as well? There might be an issue lurking in there as well.
Another way to help troubleshoot this issue could be by taking a thread dump when the container is locked up. You should be looking out for lots of threads being stuck at the same point in the code. Also, you have set fairly high queue sizes in some of the executor configurations. That will mean you have to have e.g. 2048 tasks pending before the container will actually spin up another thread to handle the load. If the thread dump shows a lot of threads waiting on sendSync(), you might want to consider lowering the queue size so the container becomes a bit more eager in adding threads to the pool. ----- Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ -- View this message in context: http://servicemix.396122.n5.nabble.com/ExchangeTimeoutException-tp4520535p4535229.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
