Bug 1210365

Summary: [GSS] (6.4.z) response.setBufferSize() has no effect when using the response writer
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Aaron Ogburn <aogburn>
Component: WebAssignee: baranowb <bbaranow>
Status: CLOSED CURRENTRELEASE QA Contact: Radim Hatlapatka <rhatlapa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: bbaranow, cdewolf, jawilson, rhatlapa
Target Milestone: CR2   
Target Release: EAP 6.4.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1212566 (view as bug list) Environment:
Last Closed: 2017-01-17 09:56:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1188828, 1207953, 1212566    

Description Aaron Ogburn 2015-04-09 14:11:13 UTC
Description of problem:

This is the same issue as https://issues.apache.org/bugzilla/show_bug.cgi?id=55842

When using the response writer, we end up just flushing the buffer in org.apache.catalina.connector.OutputBuffer.realWriteChars instead of trying to grow the buffer.


Version-Release number of selected component (if applicable):

Web 7.5.7


How reproducible:

Always

Steps to Reproduce:
1. response.setBufferSize(#) to increase buffer size
2. response.getWriter() and write data greater than the initial buffer size but less than the increased buffer size
3. check response.isCommitted() to see that the data has already been flushed and the response committed instead of the buffer's being expanded


Actual results:

Buffer is flushed upon reaching the initial buffer size instead of growing up to the buffer limit increased by response.setBufferSize(#)


Expected results:

Buffer grows up to the increased limit when using the response writer


Additional info:

Fix for 7.5.x: r2603

Comment 2 Rostislav Svoboda 2015-04-21 14:50:55 UTC
We have received one-off patch this week, there are some troubles with patch file, but the functionality is fixed. We need to include this into the payload to prevent regressions.

Comment 4 Rostislav Svoboda 2015-04-23 11:55:49 UTC
Re-acking after "qa_ack flag reset for and jboss-eap-6.4.0 and jboss-eap-6.4.z items" cleanup.

Comment 5 Radim Hatlapatka 2015-05-14 12:50:27 UTC
Verified with EAP 6.4.1.CP.CR2

Comment 6 Petr Penicka 2017-01-17 09:56:53 UTC
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.