Legacy Knowledge Base
Published Sep. 10, 2025

Session timeout auto extend fails with Google Chrome

Written By

Katalin Györgyövics

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

  • The user session expires in about 10-15 minutes inactivity, even if session.timeout.auto.extend is set to true, and session.timeout and session.timeout.auto.extend.offset are all configured. The issue only occurs when using Google Chrome.

Environment

  • DXP 7.3

Resolution

  • The issue happens when the setInterval in Liferay's session.js file dramatically slows down. Since the interval is not checked in a period of a minute, by the time session would be extended, it is already expired in the server. The session expiration happens only with Google Chrome and typically when the session.timeout is low (e.g. 2 minutes) and session.timeout.auto.extend.offset is less than 60.
  • To maintain the session please follow the below workaround: increase the session.timeout.auto.extend.offset to above 60 (one minute) and the session.timeout above 2. For example, add these values to your portal-ext.properties file:
session.timeout=3
session.timeout.auto.extend=true
session.timeout.auto.extend.offset=70

Additional Information

 

Did this article resolve your issue ?

Legacy Knowledge Base