Hi Ralph > I attached the server log file. > I asked my administrator to create a tcp trace and will forward it as > soon as I get it. Here is a filtered snippet of the log: 2009-09-02 16:59:32,307 DEBUG [org.apache.synapse.transport.nhttp.ServerHandler] HTTP connection [/127.0.0.18:46523]: GET /soap/ HTTP/1.1 2009-09-02 16:59:32,310 DEBUG [org.apache.synapse.transport.nhttp.ServerHandler] HTTP connection [/127.0.0.18:46523]: Output ready 2009-09-02 16:59:32,311 DEBUG [org.apache.synapse.transport.nhttp.ServerHandler] HTTP connection [/127.0.0.18:46523]: Content encoder [chunk-coded; completed: false] ..... 2009-09-02 16:59:32,313 DEBUG [org.apache.synapse.transport.nhttp.ServerHandler] HTTP connection [/127.0.0.18:46523]: Content encoder [chunk-coded; completed: true] 2009-09-02 16:59:32,313 DEBUG [org.apache.synapse.transport.nhttp.ServerHandler] HTTP connection [/127.0.0.18:46523]: Response ready 2009-09-02 17:01:33,278 DEBUG [org.apache.synapse.transport.nhttp.ServerHandler] HTTP connection [/127.0.0.18:46523]: Timeout
It seems like you issue a GET /soap/ request? I also saw many of those.. what is the purpose of issuing that? Anyway.. this seems like a harmless possible bug - where the connection gets timedout - but Synapse thinks its response was not fully read by the client. This could happen if the client just looks at the header of the response, and does not read the entity body - which will prevent the HTTP connection from being re-used again (i.e. as a keepalive) - however, I also suspect a slight bug in the code where this message could be dumped in a harmless case. Do you see an actual error at the client side? cheers asankha -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com
