legacy-knowledge-base
Publicado Jun. 25, 2030

Unable to publish the web content with huge data

written-by

Pooja Bhambani

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

learn-legacy-article-disclaimer-text

Issue

  • Steps to reproduce:
    1.
    Start Liferay DXP 7.4
    2.
    Navigate to Web Content under Content & Data.
    3. Go to structure and add three 'Rich Text' fields with repeatable. Click Save.
    4. Create web content with the created structure.
    5.
    Enter the data. Please make sure to enter the 40-50 entries in the repeatable field.
    6.
    Try to publish the web content.

    Actual Result: Web content is not publishing and showing the below WARN in the console.

    2022-09-28 10:06:50.093 WARN [http-nio-8080-exec-10][code_jsp:159]
    {code="400", msg="", uri=/o/dynamic-data-mapping-form-context-provider/}
    

    Expected Result: Web content must be published with huge data.

Environment

  • Liferay DXP 7.4

Resolution

  • When adding a large amount of data to web content, it surpasses the request limit.
  • To overcome the issue, user must include the following property in the portal-ext.properties file.
## Upload Servlet Request
#
# Set the threshold size to prevent extraneous serialization of uploaded
# data.
#
# Env: LIFERAY_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_UPLOAD_PERIOD__UPPERCASEF_ILE_UPPERCASEI_TEM_PERIOD_THRESHOLD_PERIOD_SIZE
#
com.liferay.portal.kernel.upload.FileItem.threshold.size=8048576

Additional Information

  • Configure the portal-ext.properties file with the above property and restart the server to see the changes.  
  • Kindly check the behavior in the lower environment first, if everything works as expected then move to production as per your discretion if you feel comfortable with it.
  • LPS-163222
did-this-article-resolve-your-issue

legacy-knowledge-base