<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi Harm <blockquote cite="mid:f822aa1f0902250633u21be4a74n2d308c7abd0f5b73@mail.gmail.com" type="cite">The problem was most definately in the ESB code. The ESB got into a state where it didn't handle any messages anymore (deadlock). It also didn't handle any other messages for _other_ backends anymore. Only restarting the ESB worked. Meanwhile the backend (running on a separate tomcat) the was still working. (without any restart). workaround whenever I fooled the ESB that the backend was running on a different machine the ESB ran fine.(it really was still running on the same machine (but rather then accessing it via 'localhost'   rerouting the traffic really through an other machine, where apache routing the traffic back) (so: ESB configuration has an endpoint on <a moz-do-not-send="true" href="http://someotherhost/.">http://someotherhost/.</a>..   on someother host apache proxies the traffic back to the ESB host.) Note: maybe this ticket has nothing to do with the original question on WSAS/ESB on the same machine. I'm not sure. </blockquote> The NIO code has a slight probability to behave differently with clients on the same physical host and others - and this depends mainly on the OS. (e.g. I first saw this couple of years ago with a very old Sun Solaris). I do not want to comment on this specific issue without further analysis, but like Ruwan said, quite a few issues have been fixed on the trunk after the Synapse 1.2/ESB 1.7.x releases, with help mainly from real users who use it in production cheers asankha <pre class="moz-signature" cols="72">-- Asankha C. Perera AdroitLogic, <a class="moz-txt-link-freetext" href="http://adroitlogic.org">http://adroitlogic.org</a> <a class="moz-txt-link-freetext" href="http://esbmagic.blogspot.com">http://esbmagic.blogspot.com</a> </pre> </body> </html>