Legacy Knowledge Base
Published Jul. 2, 2025

How do I resolve a Tika WriteLimitReachedException error?

Written By

Madeleine Clay

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • I am seeing the following error:
    org.apache.tika.sax.WriteOutContentHandler$WriteLimitReachedException: Your document contained more than 1048576 characters, and so your requested limit has been reached. To receive the full text of the document, increase your limit. (Text up to the limit is however available).

Environment

  • DXP 7.2
  • DXP 7.3

Resolution

  • The Tika write limit is set in bytes by the following property:
    #

    # Set the maximum size for a file's indexable content. Files larger than

    # this property will only have this amount of their content indexed. A value

    # of -1 indicates that all of a file's content will be indexed. A value of 0

    # indicates that none of the file's content will be indexed.

    #

    dl.file.indexing.max.size=1048576
  • Increasing the indexing limit set by this property in portal-ext.properties will increase the Tika write limit, avoiding the error by allowing the full text of the affected document to be indexed.

Additional Information

 

Did this article resolve your issue ?

Legacy Knowledge Base