The workaround for this problem was in my case to get input stream on client side e.g. like this: [...] sender.close(); InputStream inputStream = connection.getInputStream(); inputStream.close();
Jetty error still occurs in the log file, but the message is now routed to jms component. Without it message wasn't forward by http component. This is very strange, as MEP is set to in-only so http-component should only accept input. -- View this message in context: http://www.nabble.com/http-endpoint---connection-forcibly-closed-tf4676702s12049.html#a13384562 Sent from the ServiceMix - User mailing list archive at Nabble.com.
