How to improve "idle in transaction" state in PostgreSQL?
Written By
Sebastian Madaras
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 user encounters a state where a specific update is not being executed.
- The system hangs and the specific process cannot finish.
- Hanging transactions in the database that can only be unblocked if you restart the server.
- Issue could be more specific for Cloud base environments.
Environment
- Liferay Cloud
- Liferay DXP 7.4
Resolution
- As a workaround experiment with the configuration parameter "idle_in_transaction_session_timeout =". This is used to control the maximum time a session can remain idle while in a transaction. Be aware that this parameter can impact long-running transactions that are legitimate.
- A solution for the case was created. Update your system to the latest Liferay DXP 7.4 quarterly release:
DXP 2023.Q4.3 Patch Release
Did this article resolve your issue ?