Skip navigation
Currently Being Moderated

Tomcat exception Cannot call sendError() after the response has been committed

Jul 31, 2012 7:19 PM

Tags: #developer #cf10; #tomcat; #edition; #senderror

CF 10 Developer Edition.


Windows XP SP3


When submitting a page that worked fine in CF 7 on this machine, I get an error I've never seen before:





description: The server encountered an internal error () that prevented it from fulfilling this request.




javax.servlet.ServletException: ROOT CAUSE: java.lang.IllegalStateException: Cannot call sendError() after the response has been committed at org.apache.catalina.connector.ResponseFacade.sendError(ResponseFacade .java:451) at javax.servlet.http.HttpServletResponseWrapper.sendError(HttpServletRe at at coldfusion.filter.FormScope.parseQueryString(


etcetera, which ends in


note The full stack trace of the root cause is available in the Apache Tomcat/7.0.23 logs.



I can't seem to be able to debug or localize this error: cfabort placed in strategic places doesn't help at all, and none of my usual tricks work. The debug info is not displayed when this error happens (although the server is set to display debug info, and it normally does).


Totally puzzled,



  • Currently Being Moderated
    Jul 31, 2012 7:26 PM   in reply to paperno3

    Perhaps adjust Maximum number of POST request parameters from say 100 to 500.


    CF10admin > Server Settings > Settings > Request Size Limits > Maximum number of POST request parameters > value


    Not sure you may need to restart CF10 for change to apply.


    HTH, Carl.

    Mark as:
  • Currently Being Moderated
    Oct 11, 2012 9:02 AM   in reply to paperno3

    First, this discussion fixed my problem.  Customers of ours had a number of forms with more than 100 fields.  This is CF setting is new and honestly, I think 100 is too low.  500 should be the default.


    it's not cool to find out about this option from errors in a production server.   Better to make the default higher, then admins can lower it if they want rather than cause chaos until this new buried option is discovered.


    Please Adobe consider increasing this default value, while on the surface it's seemingly high, we have a product that creates a lot of hidden fields...

    Mark as:
  • Currently Being Moderated
    Oct 1, 2013 5:52 AM   in reply to dlangh

    As stated above, not cool to find out about this in prod! This option is a real pain in... well, you know where!

    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points