Hi Oleg, Thanks for your reply, which already helped me a little bit to improve my understanding.
> I am very sorry but we currently have almost nothing in terms of > documentation for HttpCore. I am planning to start working on an > HttpCore tutorial in August. Oh yes, a tutorial would be very helpful. I'll be one of the first who is going to read it. :-) > Asankha knows best about the Synapse NIO transport. I'll happily chip > in information about HttpCore internal stuff Thanks Oleg! That's why I included the http components dev list. > > org.apache.http.nio.util.SharedOutputBuffer.flushContent() is waiting > > for some notification. Who is responsible for that notification? > It expects a notification from the I/O reactor it is ready to accept > more output. > > Does anybody know something about possible causes for not getting such a > > notification? > The most likely explanation the output notifications have been suspended > by the protocol handler (Synapse it this case). Apparently Synapse > thinks it is not meant to be producing any output at this point) Hmm, this sounds interesting. So to translate this, the protocol handler implementation is: HttpCoreNIOSender or ClientHandler? Asankha wrote me, that he is also already working on our issue and has some idea. So'll wait what he finds out. I would be really happy if I were able to reproduce the issue at will. Unfortunately I'm not able to do this, so I have no test case. It just happens from time to time and then Synapse accepts new requests which get executed at the destination service, but the client never receives a reply, as the client worker threads are all waiting to sent out their message. Regards, Eric
