Slow Page Rendering of Large Pages Due to HTTP POST Limitations

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.

Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

There is no maximum limit stipulated on a page size in Confluence. However, if a page larger then 2Mb is created, a user may experience two problems:

  1. Rendering of a page is slow. Understandably, rendering of a large page is going to take excessive time. Don't try to put the entire content of a book into one page, split it into pages/chapters. It is easier to manage and fast to render too.
  2. One of the following errors occurs in the logs:

    Tomcat 5.5.x
    java.lang.IllegalStateException: Post too large
     at org.apache.catalina.connector.Request.parseParameters(Request.java:2361)
    
    Tomcat 6.x
    Sep 2, 2010 9:33:30 AM org.apache.tomcat.util.http.Parameters processParameters
    WARNING: Parameters: Invalid chunk ignored.

    Cause

    This error manifests for large pages, on the order of 2 MB or more. Apache Tomcat 5, by default, sets the maximum size of acceptable HTTP POST request to 2MB.

    Resolution

    You can reconfigure Tomcat to accept larger requests. This can be done by increasing the allowable limit or just simply disabling this functionality.

    1. Edit is <Tomcat-Dir>/server.xml.
    2. Set the Tomcat configuration parameter maxPostSize for the HTTPConnector to a larger value (in bytes) to increase the limit. Setting it to 0 will disable the size check.

      If you are using Confluence 5.8.13 (Tomcat 8.0.24 or above), do not change the setting to 0. In Tomcat 8.0.24, the meaning of the value zero for the  maxPostSize  has been changed to mean a limit of zero rather than no limit to align it with  maxSavePostSize  and to be more intuitive. See Tomcat 8.0.24 change log for more details. You must now use  maxpostsize="-1" for unlimited size.

      See the Tomcat Configuration Reference for more information:

      maxPostSize - "The maximum size in bytes of the POST which will be handled by the container FORM URL parameter parsing. The feature can be disabled by setting this attribute
      to a value inferior or equal to 0. If not specified, this attribute is set to 2097152 (2 megabytes)."

      You can check the Tomcat version bundled with your Confluence instance in KB Bundled Tomcat and Java versions

    3. If using Apache web server, add the same parameter to the AJP connector instead.


Last modified on Dec 20, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.