Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Environment becomes unstable after number of file descriptors has steadily increased

Written By

Ricardo Couso

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

  • A Liferay environment with a frontal element has become unstable after running for a few days.
  • Checking the system's health, there has been a steady increase of open file descriptors.

Environment

  • Liferay DXP 7.4
  • Liferay Quarterly Release 2023.Q3, 2023.Q4

Resolution

  • This behavior can occur when there's a frontal element to Liferay communicating via AJP. 
  • The connections between them will show as open file descriptors in the system.
    • They can be displayed with the command lsof -p $java_pid.
  • For example, Tomcat can connect to a frontal element by configuring in the file $TOMCAT_HOME/conf/server.xml the element 
    <Connector protocol="AJP/1.3" [...] />
  • The Connector timeout attributes connectionTimeout and keepAliveTimeout might not be set, so they'll have a default infinite value. This can lead to an increasing number of established connections between the frontal making Liferay unstable.
  • Make sure to establish the connectionTimeout and/or keepAliveTimeout attributes with values adequate to your environment.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?