Legacy Knowledge Base
Published Jun. 30, 2025

What does the TempFileEntriesMessageListener actually do?

Written By

Sorin Pop

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

  • In our logs we see some errors apparently related to an hourly job, TempFileEntriesMessageListener
  • the triggering interval of this job seems to be set in System Settings/ Documents and Media/Service/Temporary File Entries Check Interval, and it is set to 1 hour by default, but I am not sure what this job actually does.

Environment

  • 7.4

Resolution

  • What does the TempFileEntriesMessageListener actually do?

    To illustrate this please consider the following steps (this is just an example, such temp files can also come from other places than blogs):

    1. Go to Content & Data - Blogs

    2. Add a new Blogs entry

    3. Drag and drop in multiple different images for the cover image

    4. At this point check the DLFileEntry table (SELECT * FROM DLFileEntry)

      1. Note that there are several entries all with a similar repositoryId

      2. Checking the Repository table (SELECT * FROM REPOSITORY) these file entries belong to the com.liferay.portal.kernel.util.TempFileEntryUtil repository

    5. Publish the blog

    6. Again, check the DLFileEntry table

      1. Note that the last image uploaded to the blog now has a different repositoryId

      2. Checking the Repository table this new entry is now associated with the com.liferay.blogs repository

    After following these steps we now have a single image associated with the blogs entry and several images that were temporarily uploaded but ultimately never used. It is these file entries that are removed by the TempFileEntriesMessageListener.

 

Did this article resolve your issue ?

Legacy Knowledge Base