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]>
