Cannot set header. Response already committed.

Hello i was wondering if any of you folks ever wittnessed the following error in Websphere 3.5.

[01.03.13 16:09:36:343 EST] 1058f2c WebAppInvoker X Unexpected internal engine error while processing request
                                 java.lang.IllegalStateException: ERROR: Cannot set header. Response already committed.
        at java.lang.Throwable.fillInStackTrace(Native Method)
        at java.lang.Throwable.fillInStackTrace(Compiled Code)
        at java.lang.Throwable.<init>(Compiled Code)
        at java.lang.Exception.<init>(Compiled Code)
        at java.lang.RuntimeException.<init>(Compiled Code)
        at java.lang.IllegalStateException.<init>(IllegalStateException.java:45)
        at com.ibm.servlet.engine.srt.SRTServletResponse.setHeader(Compiled Code)
        at com.ibm.servlet.engine.srt.SRTServletResponse.setContentType(Compiled Code)
        at com.ibm.servlet.engine.srt.SRTServletResponse.initForNextResponse(Compiled Code)
        at com.ibm.servlet.engine.srt.SRTConnectionContext.prepareForNextConnection(Compiled Code)
        at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(Compiled Code)
        at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(Compiled Code)
        at com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(Compiled Code)
        at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(Compiled Code)
        at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(Compiled Code)
        at com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(Compiled Code)
        at com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(Compiled Code)
        at com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(Compiled Code)
        at com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRunnable.notifyService(Compiled Code)
        at com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRunnable.run(Compiled Code)
        at com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run(Compiled Code)
        at java.lang.Thread.run(Thread.java:479)

This is happening when i try to click on any url that points to a servlet.
Any url that points to a jsp does not have this problem at anytime.
This here only happens SOMETIMES and i am having trouble making it occure repeatedly.
Thanks
Heath

Heath,
I think you are setting some attributes or invoking some methods on the Response which should have been done earlier.

Could you please post your source code here? I'm quite interested in this problem.
------------------
Tony Chen
SCJP, ICS & ICSD (WebSphere)

Well as it turned out there were 2 things happening.
1. In bootstap.properties the ose.single.thread parameter was set to true...(ose.single.thread=true). We set this to false and the problem is now happening MUCH less frequently. Funny though that it sets that param to false by default.
2. Also we only had version 3.5.2. Someone in the WASug said that they had the same problem we did...When they first released there application everything was fine, but as server usage increased they got that error. That was about the time the fix pack was released (about a month and a half ago), anyhow after they went to Websphere 3.5.3 there were no problems.
We intentionally didn't want to install the fix pack until we were sure it wouldn't hurt our production apps... We just never got the time to go back and install it.
We are installing the fixpack this week so i will post any findings we uncover.
Heath
[This message has been edited by Heath Lilley (edited May 14, 2001).]
[This message has been edited by Heath Lilley (edited July 26, 2001).]

Better late than never...
Installing fix pack 3.5.3 over 3.5.2 only helped matters. There were no visible errors after the change.
Fixpack 3.5.3 also fixes the ose.single.thread issue discussed above.
If you are running 3.5 and you want to go to 3.5.3, I don't think you need to install fixpack 3.5.2. I beleive you can go straight to 3.5.3.

Hi Folks,
I too face the problem does it occur on all the areas or only in particular area. I get this error in particular area only.
If we upgrade the fix pack will it solve the problem.
cheers guys,