aspose file tools*
The moose likes Websphere and the fly likes SessionAffinityManager setCookie SESN0066E: The response is already committed to the client. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "SessionAffinityManager setCookie SESN0066E: The response is already committed to the client." Watch "SessionAffinityManager setCookie SESN0066E: The response is already committed to the client." New topic
Author

SessionAffinityManager setCookie SESN0066E: The response is already committed to the client.

Ionut Barau
Greenhorn

Joined: Feb 18, 2008
Posts: 20
Hi guys,

I am using WAS 7.0.0.17 and JSF 2.0+ Richfaces 4. I keep getting this error :The response is already committed to the client.
I have a single page that is rendered, but when i click the button mapped to the managed bean method nothing happens. Last night the app was working without any problem. This morning it stopped, and the only modification i did was configuring WAS to stop publishing automatically. I really don't have a clue what might be the problem. I guess the session expires right after the page is rendered..Tried with no expiring session but still nothing

Error:

WASSessionCor W SessionAffinityManager setCookie SESN0066E: The response is already committed to the client. The session cookie cannot be set.
srt W com.ibm.ws.webcontainer.srt.SRTServletResponse addSessionCookie WARNING: Cannot set session cookie. Response already committed


I addition when i first run the app it throws:

context W JSF1091: No mime type could be found for file combo_list_shadow.png. To resolve this, add a mime-type mapping to the applications web.xml.

really don't know what is up with this one ...i don't have any png file..maybe from richfaces calendar i think

If you need code just let me know.




Thanks
Ionut Barau
Greenhorn

Joined: Feb 18, 2008
Posts: 20
Hy guys

I am still struggling with this problem...

I've tested the application on JBoss 6 and everything works fine...After searching deeper i have found that the core problem is actually that JSF is not able to save the state on server. if I configure the application to save the state of the page on client everything works just fine. So the problem in my opinion is due to some WAS configuration issue, not the code as I have expected...If i save the state on server, click a h:commandLink will throw View could not be restored error.

Bellow is my web.xml file:





My faces-config file contains only the dtd schema for 2.0 version


my page is bellow:





i am stuck on this one for a while so I appreciate any help

Thanks


 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: SessionAffinityManager setCookie SESN0066E: The response is already committed to the client.