Re: Closed Input Stream across firewall

My only guess is the firewall times the connection out on inactivity. So if the servlet needs to do additional processing before the response is sent and the time is too long - the firewall might drop the connection. -Tim Vineet Chopra wrote: I am not calling getParameter method, instead

Re: Closed Input Stream across firewall

The firewall is not the problem. If you are using ServletRequest.getInputStream() - you cannot use ServletRequest.getParameter(). Odds are something is calling getParameter() which in turn getParameter() reads the input stream and makes it unavailable. -Tim Vineet Chopra wrote: I am using a

Re: Closed Input Stream across firewall

I am not calling getParameter method, instead request.getInputStream() to read the incoming XML is the first line of code after a few logging statements. Code for the sender servlet is as follows - URL url = new URL(destinationURL); URLConnection conn = url.openConnection();

Closed Input Stream across firewall

I am using a web application deployed on Tomcat 4.0 to receive and route incoming XML messages to destination web application also deployed on Tomcat 4.0. A firewall exists between these servers. All firewall policies are enabled for incoming and outgoing traffic. The ServletInputStream is