On Mon, Mar 2, 2015 at 5:25 PM, Umesh Sehgal <umesh.seh...@gmail.com> wrote:
> > > > On Mon, Mar 2, 2015 at 3:52 PM, Rainer Jung <rainer.j...@kippdata.de> > wrote: > >> Am 02.03.2015 um 11:02 schrieb Umesh Sehgal: >> >>> 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? >>> >> >> Please do not top post. For the rest see below. >> >> 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 >>>> >>> >> Could it be "If a request that includes an Expect: 100-continue header >> receives anything other than a 2xx response, close the connection This >> protects against misbehaving clients that may not sent the request body in >> that case and send the next request instead. (markt) "? >> >> It was changed in 7.0.49, but 49 was not released, so 50 was the first >> version with this change. >> >> >> Regards, >> >> Rainer >> > > I did see this in changelog but in the captured traffic don't see any > expect 100 header request. Any other way I can confirm this on the tomcat > side? > > Thanks, > Umesh > Can you please point me to SVN change for : "If a request that includes an Expect: 100-continue header receives anything other than a 2xx response, close the connection This protects against misbehaving clients that may not sent the request body in that case and send the next request instead. (markt) "? Thanks, Umesh
