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.
Cause
When ESI caching is enabled, the flushBuffer does not adhere to the API specification and the response is not committed. Other APIs, such as setContentType, will be accepted until servicing is complete and the content is flushed.
Environment
WebSphere 8.0.0.8 ND
Diagnosing The Problem
Web container, and dynamic cache trace along with plugin trace.
Resolving The Problem
If the customer is not using ESI, disable ESI cache.
Historical Number
N/A
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21678191