Bug 1210365 - [GSS] (6.4.z) response.setBufferSize() has no effect when using the response writer
Summary: [GSS] (6.4.z) response.setBufferSize() has no effect when using the response ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR2
: EAP 6.4.1
Assignee: baranowb
QA Contact: Radim Hatlapatka
URL:
Whiteboard:
Depends On:
Blocks: 1188828 eap641-payload 1212566
TreeView+ depends on / blocked
 
Reported: 2015-04-09 14:11 UTC by Aaron Ogburn
Modified: 2019-06-13 08:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1212566 (view as bug list)
Environment:
Last Closed: 2017-01-17 09:56:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBWEB-312 0 Major Closed response.setBufferSize() has no effect when using the response writer 2018-12-26 08:35:04 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.