Legacy Knowledge Base
Published Jun. 30, 2025

SystemEvent table might accumulate in size over time

Written By

Dávid Hegedüs

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

  • You might encounter a behavior where your SystemEvent table has increased to a size which you deem troublesome.
  • The SystemEvent table contains the deletion events of assets for Staging. These events can be exported/published.  

Environment

  • Liferay DXP 7.0+

Resolution

  • The solution is to set the following portal properties as required to regularly clean the entries:
        # Set the interval in hours on how often CheckSystemEventMessageListener
    # will run to check for and delete system events that have been reached the
    # maximum age.
    #
    # Env: LIFERAY_STAGING_PERIOD_SYSTEM_PERIOD_EVENT_PERIOD_CHECK_PERIOD_INTERVAL
    #
    staging.system.event.check.interval=24
    #
    # Set this to the maximum age (in number of hours) that a system event will
    # be kept. Note that these settings may be overridden in Portal Settings for
    # each portal server or in Site Settings for each site.
    #
    # Env: LIFERAY_STAGING_PERIOD_SYSTEM_PERIOD_EVENT_PERIOD_MAX_PERIOD_AGE
    #
    staging.system.event.max.age=0
  • Setting staging.system.event.max.age=0 will prevent the entries from timing out.

Additional Information

 

Did this article resolve your issue ?

Legacy Knowledge Base