Troubleshooting
Problem
The J2EE flushBuffer API specification is not adhered to when servlet/command caching and esi caching are enabled. Invoking flushBuffer does not commit the response.
Symptom
An application may continue to add headers or set content length that normally would be rejected because the response is committed when flushBuffer is invoked.
[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Dynamic Cache","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.0","Edition":"Base;Network Deployment","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Historical Number
N/A
Was this topic helpful?
Document Information
More support for:
WebSphere Application Server
Software version:
8.0
Operating system(s):
AIX, HP-UX, Linux, Solaris, Windows
Document number:
515855
Modified date:
03 March 2025
UID
swg21678191
Manage My Notification Subscriptions