Win a copy of Think Java: How to Think Like a Computer Scientist this week in the Java in General forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Response already committed

 
Picus Ameradeus
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

I have deployed a struts app on a tomcat server, which has been deployed successfully on other (staging server).

However, on this new server, when I try to load the app, I get the following error:

org.apache.jk.server.JkCoyoteHandler action
INFO: response already committed

In general, I know what causes this error, the app has been sent the response and it thinks it is being sent again.

I just would like to know how to correct it, and what common causes are.
 
Brent Sterling
Ranch Hand
Posts: 948
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't know what is going on in your case. I can mention a case where I saw this message on my project. Another developer put security roles in web.xml on jsp files in certain directories. That sounded like a reasonable solution. The problem is that since we use tiles, certain tiles on the page (like the header tile) have already been rendered by the time the jsp is accessed. When the jsp was accessed the container tried to redirect to an error page but since part of the response has already been committed we got this error message instead.

- Brent
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic