File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Struts and the fly likes Blank page in browser - Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Frameworks » Struts
Bookmark "Blank page in browser - "Response already committed" in logs" Watch "Blank page in browser - "Response already committed" in logs" New topic

Blank page in browser - "Response already committed" in logs

Pekka Parhi

Joined: May 03, 2004
Posts: 2
Hi everyone,
While testing my Struts web app, I occasionally receive blank pages in the browser window and "Response already committed" messages into the log file. The format of the message in the log file is just like this: "Apr 29, 2004 1:45:53 PM org.apache.jk.server.JkCoyoteHandler action - INFO: Response already commited" without any stack trace. This happens very randomly and there are no particular situations where and when it occurs.
I'm not writing anything to the response in my Action classes until just calling at the end of the Actions' execute methods. In the error case, when a submit button is clicked on jsp page, the execute method of an Action class is processed normally - but instead of a target jsp page where the control was forwarded, a blank page will be shown in the browser. I wonder what causes this quite strange problem.
I'm using Struts 1.1 and Tomcat 5.0.19. Could one of these cause the problem?

Marc Peabody
pie sneak

Joined: Feb 05, 2003
Posts: 4727

Usually when I receive the blank page it is because the forward is not correct. It is case sensitive, that could be a cause.
Your particular error, though, sounds like a Tomcat problem (Memory or connector issue perhaps ). That forum might be better suited.

A good workman is known by his tools.
Jiemme M.

Joined: Oct 04, 2005
Posts: 1
The "Response already commited" JK log usually happens when the client's browser requests a document that does not exist on your server (ie. invalid <img src="wrongurl"> tags in your HTML pages, non-existent javascript files, invalid css links, etc).

Mine usually appeared in my calls to MM_preloadImages()...
I agree. Here's the link:
subject: Blank page in browser - "Response already committed" in logs
It's not a secret anymore!