Created attachment 1225097 [details] fileupload example application Description of problem: A new parameter maxSwallowSize (org.apache.coyote.MAX_SWALLOW_SIZE) was introduced since EAP 6.4.7 by BZ#1236910. Some fileupload application fails silently when hitting the parameter. There's no logging out in server.log even if we increase logging level of JBossWeb. Please improve logging output to make investigation easily and for end user to know they are hitting the parameter. Version-Release number of selected component (if applicable): JBOSSWEB_7_5_15_FINAL or later How reproducible: Anytime when hitting maxSwallowSize Steps to Reproduce: 1. Deploy an attached example: spring-fileupload.war 2. Access http://localhost:8080/spring-fileupload/ 3. Upload a large file than 2MB (default value of maxSwallowSize) You will see "connection reset" error page of browser as expected. Actual results: No log message was output in server.log even if increasing JBossWeb logging level to TRACE Expected results: A log message "Maximum swallow size is exceeded" should be output in server.log Additional info: IdentityInputFilter and ChunkedInputFilter throw IOException with a log message "Maximum swallow size is exceeded" but Http11(|Nio|Apr)Processor never output the log message when catching the IOException.
Created attachment 1225098 [details] JBOSSWEB_endRequest_IOException_logging.patch
Created attachment 1225099 [details] JBOSSWEB_maxSwallowSizeExceeded_logging.patch
I have two proposed patches. I'm not sure which one is better. - JBOSSWEB_endRequest_IOException_logging.patch This will add DEBUG level logging when catching IOException in Http11(|Nio|Apr)Processor#end(). - JBOSSWEB_maxSwallowSizeExceeded_logging.patch This will add DEBUG level logging when detecting maxSwallowSize exceeded inside IdentityInputFilter and ChunkedInputFilter.
Verified with EAP 6.4.14.CP.CR1
Released with EAP 6.4.14 on March 14 (ZIPs) and March 22 (RPMs).