WAS log file flooding: WARNING: Cannot set status. Response already committed
Hi together,
I'm running JTS on WAS 8.5.x and am getting flooded with the following warning in my SystemOut.log.
I have JTS,RTC and QM deployed on the server. None of my other WAS profiles show this warning.
Does anyone know what this message indicates?
[5/21/14 10:14:41:702 EDT] 000000d6 srt W com.ibm.ws.webcontainer.srt.SRTServletResponse setStatus WARNING: Cannot set status. Response already committed.
[5/21/14 10:15:42:688 EDT] 000000ff srt W com.ibm.ws.webcontainer.srt.SRTServletResponse setStatus WARNING: Cannot set status. Response already committed.
[5/21/14 10:16:43:686 EDT] 0000010f srt W com.ibm.ws.webcontainer.srt.SRTServletResponse setStatus WARNING: Cannot set status. Response already committed.
[5/21/14 10:17:44:746 EDT] 000000fc srt W com.ibm.ws.webcontainer.srt.SRTServletResponse setStatus WARNING: Cannot set status. Response already committed.
[5/21/14 10:18:45:712 EDT] 000000ff srt W com.ibm.ws.webcontainer.srt.SRTServletResponse setStatus WARNING: Cannot set status. Response already committed.
[5/21/14 10:19:46:684 EDT] 000000fe srt W com.ibm.ws.webcontainer.srt.SRTServletResponse setStatus WARNING: Cannot set status. Response already committed.
2 answers
Based on what you have described and your environment, it looks like there is a workaround in a CLM QM 5.0 article that would also apply to 4.0.5, here: https://jazz.net/library/article/1419#111514
Comments
Kevin Ramer
May 21 '14, 11:26 a.m.Donald Nong
May 22 '14, 12:44 a.m.Kevin Eifinger
May 22 '14, 3:08 a.m.Guido Schneider
May 22 '14, 4:55 a.m.