||Two Servlet Filters Every Web Application Should Have|
|Subject:||GZip Filter, IBM WAS 5 -- Cannot set header. Response already committed|
Response to: GZip Filter, IBM WAS 5 -- Cannot set header. Response already committed
Hi George, I saw this same warning on WAS 5 seemingly caused by one jsp forwarding to another, or in my case I had the filter turned on for both .jsp and servlets - I saw this warning when my servlet forwarded to a jsp. Since my webapp is a MVC type I really only have 1 servlet and it handles 99.9% of all requests, so I just turned the filter off for .jsp files and it went away. Well, mostly - I still see it sporadically when running under heavy load.
Showing messages 1 through 2 of 2.