Hmm. The fact that you only get this behaviour in 3.3 suggests very strongly a problem in that release. Is there any reason why you can't use a different release and avoid the error?
That aside, I have seen this error under different circumstances - doing a response.sendredirect in a JSP _after_ having already output HTML to the browser. For this to error is fair enough - its supposedly outside the HTTP spec. to send redirects after having started outputting HTML (in ASP, MS being the hand-holders that they are, attempting to do this throws a runtime error so as to avoid unexpected behaviour). Could your code be construed as doing something similar? If yes, then you cannot guarantee that it will work on all combintaions of browser and server. ian ----- Original Message ----- From: "Vincent Massol" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, December 21, 2001 2:44 PM Subject: [Tomcat 3.3] Strange behaviour w/ mixed POST/GET request > I have a strange behaviour in Tomcat 3.3 that does not happen either in > Tomcat 4.x or in Tomcat 3.2.x (or any other servlet engine for the > matter : Orion, Resin, WebLogic). It looks like voodoo for me and I have > trouble understanding what's happening. > > I am sending several different HTTP requests (using HttpURLConnection) > to the server and depending on the order I get or do not get an error. > When I get the error, it is the typical : > > Connection aborted by peer: JVM_recv in socket input stream read > java.net.SocketException: Connection aborted by peer: JVM_recv in socket > inp > ut stream read > at java.net.SocketInputStream.socketRead(Native Method) > > I am doing one special request in which I send _both_ GET parameters (in > the URL) and parameters in the request body (POST method). The other > requests are only GET requests. > > If I call the mixed POST/GET request first, followed by the other GET > requests then everything is fine. However, if I start by doing on GET > request and then followed by the mixed POST/GET one, I get the > connection aborted by peer error. > > Any idea ? Any known issues with mixed POST/GET requests ? > > Thanks a lot for any hint as I'm beginning to tear my hair ... :-) > -Vincent > > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
