"heiko.braun(a)jboss.com" wrote : Looking at it more carefully doesn't reveal anything at JBossWS processing level. That piece of code prepares the SOAPMessageContext upon receiving the HTTPRequest InputStream. | Yes, it seems the HTTPRequest InputStream is already closed when jbossws try to use it. One more thing to clarify the situation: it happens with unpredictable frequency...it seems a problem with server overload or concurrency (just a smell of them, I'm not sure, but a lot of tests in test environment can't reproduce error) "heiko.braun(a)jboss.com" wrote : | My 2 cents: | In this case i'd say that the servlet engine probably has written something back to .NET client without notice. | and closes the connection. "heiko.braun(a)jboss.com" wrote : | Do you have any HTTP logs available at the client side? | No of course.........it's a .NET client :) "heiko.braun(a)jboss.com" wrote : | A look at the jboss-tomcat logs might help as well. Some classes suspected? We can't enable all jboss-tomcat logs in production environment processing many requests per second. A little OT: please take a look to my last post in Design Forum ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993094#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...