IBM Support

FlushBuffer does not commit the response when servlet/command caching is enabled on the application server and ESI caching is enabled on IHS.

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.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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":"LOB45","label":"Automation"}}]

Historical Number

N/A

Document Information

Modified date:
15 June 2018

UID

swg21678191

Page Feedback