Thanks for the quick reply, I tried using the maxSwallowSize with increased value but to no effect. The max size that I have been able to upload is ~16 KB. I also see that the maxSwallowSize got introduced with update 55 but the behavior I'm seeing is 50 update onwards, is there any other param too? is there any logging that can be turned on tomcat to help debug?
Thanks, Umesh Thanks, Umesh Sehgal On Mon, Mar 2, 2015 at 2:32 PM, Rainer Jung <rainer.j...@kippdata.de> wrote: > Am 02.03.2015 um 09:34 schrieb Umesh Sehgal: > > Hi, >> >> We recently upgraded our application's tomcat from 7.0.30 to 7.0.59. After >> upgrade the file upload feature has broken. I have been able to nail it >> down to the point that the problem manifests 7.0.50 onwards. Here is the >> exception that I see inside logs: >> >> Caused by: java.net.SocketException: Connection reset by peer: socket >> write error >> at java.net.SocketOutputStream.socketWrite0(Native Method) >> at java.net.SocketOutputStream.socketWrite(Unknown Source) >> at java.net.SocketOutputStream.write(Unknown Source) >> at sun.security.ssl.OutputRecord.writeBuffer(Unknown Source) >> at sun.security.ssl.OutputRecord.write(Unknown Source) >> >> Also, I notice that the problem doesn't happen with a 2KB file but 2MB. I >> don't see anything obvious in the 7.0.50 changelog which could explain >> this >> behavior. Can someone please provide some pointer as what could be causing >> this? >> > > https://bz.apache.org/bugzilla/show_bug.cgi?id=57617 > > Fixed for next 7.0.60 in > > http://svn.apache.org/r1659295 > > The original change can be found looking for "maxSwallowSize" in the > changelog > > Regards, > > Rainer > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
