User timeout session in the new Liferay 7.3.1 GA2User timeout session in the new Liferay 7.3.1 GA2https://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1190419452024-03-28T20:23:21Z2024-03-28T20:23:21ZRE: User timeout session in the new Liferay 7.3.1 GA2Olaf Kockhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1194104542020-06-16T08:03:31Z2020-06-16T08:03:31Z<div class="quote-title">Peter Andreus:</div><blockquote><br />My <a href="https://pastebin.com/gHtaed5X">Dockerfile</a> doesn't contain anything special<br />in docker-compose.yml i set:<br /> LIFERAY_SESSION_PERIOD_TIMEOUT: 120<br /> <br />I expect to have 120 min session.<br />When i check in Control Panel -> Server Administration -> Properties -> Portal Properties <br />i can see session.timeout = 120<br /><br />Hovewer after 15 min of inactivity im still logged of liferay.<br /></blockquote><br />There are two ways to set this timeout, both with different behavior: The setting you describe above tells Liferay that sessions are 120 minutes long. This way Liferay may show a notice that the session soon runs out after 119 minutes and offer to extend it.<br />The other is the (mentioned further above) configuration in web.xml. It configures when Tomcat (or any appserver) considers a session to be inactive, and allows tomcat to discard the session. After all, those sessions are maintained by the appserver. Liferay has nothing to say in session management.<br />You want both to be set to the same value (or at least have the web.xml value be slightly <em>higher</em> than Liferay's value), for proper operation. Just changing one value only works when you go lower than the default value, not higher. The lowest of these values determines your expectation for overall session length.Olaf Kock2020-06-16T08:03:31ZRE: User timeout session in the new Liferay 7.3.1 GA2Peter Andreushttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1194101222020-06-16T07:25:22Z2020-06-16T07:25:22Zbump for interestPeter Andreus2020-06-16T07:25:22ZRE: User timeout session in the new Liferay 7.3.1 GA2Peter Andreushttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1193546552020-06-10T10:10:01Z2020-06-10T10:10:01ZMy <a href="https://pastebin.com/gHtaed5X">Dockerfile</a> doesn't contain anything special<br />in docker-compose.yml i set:<br /> LIFERAY_SESSION_PERIOD_TIMEOUT: 120<br /> <br />I expect to have 120 min session.<br />When i check in Control Panel -> Server Administration -> Properties -> Portal Properties <br />i can see session.timeout = 120<br /><br />Hovewer after 15 min of inactivity im still logged of liferay.<br /><br />Maybe i messed up something in <a href="https://pastebin.com/12pc9Spb">portal-ext.properties</a> or in <a href="https://pastebin.com/ZjHdLuQ3">environment properties</a> in docker-compose.yml?Peter Andreus2020-06-10T10:10:01ZRE: User timeout session in the new Liferay 7.3.1 GA2Olaf Kockhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1193542832020-06-10T09:37:35Z2020-06-10T09:37:35Z<div class="quote-title">Peter Andreus:</div><blockquote><br />I cannot believe this is really thing in 7.3<br /><br />Im using docker and changes to files arent persistent, off course there is workaround but why liferay doesnt accept property set through ENV or through portal-ext.properties?</blockquote><br />It doesn't? Please give steps to reproduce.Olaf Kock2020-06-10T09:37:35ZRE: User timeout session in the new Liferay 7.3.1 GA2Peter Andreushttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1193539502020-06-10T08:48:11Z2020-06-10T08:48:11ZI cannot believe this is really thing in 7.3<br /><br />Im using docker and changes to files arent persistent, off course there is workaround but why liferay doesnt accept property set through ENV or through portal-ext.properties?Peter Andreus2020-06-10T08:48:11ZRE: User timeout session in the new Liferay 7.3.1 GA2Eric Dhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1190581742020-04-28T11:36:46Z2020-04-28T11:36:46ZThank you Christoph,<br /><br />You are right, it was the wrong web.xml.<br />It is now OK but maybe a comment in the wrong web.xml can help people like me to know there is another web.xml.<br /><br />Thanks for your time,<br />Eric.Eric D2020-04-28T11:36:46ZRE: User timeout session in the new Liferay 7.3.1 GA2Christoph Rabelhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1190472662020-04-27T14:29:38Z2020-04-27T14:29:38ZHmm.<br />I just tested it, with 7.3.1 GA2 on Linux with Java 8 and it works for me as expected. I changed the session-timeout in web.xml and the session.timeout in portat-ext.properties. I think, the portal-ext propteries setting only is relevant for the frontend, for the warning and session timeout message. The setting in tomcat/webapps/ROOT/WEB-INF/web.xml sets the actual session timeout.<br />Can you check the web.xml again?<br />Since your post is unclear, there are two web.xml files. There is another one in tomcat/conf/. Editing that one only sets only the default timeout.Christoph Rabel2020-04-27T14:29:38ZUser timeout session in the new Liferay 7.3.1 GA2Eric Dhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1190419442020-04-25T22:02:31Z2020-04-25T22:02:31ZHi,<br /><br />With the new Liferay 7.3.1 GA2 version it seems that modify user session timeout is impossible.<br />We are using the liferay tomcat bundle. And we have the same problem on windows or unix.<br />We have modify our portal-ext.properties and add this line :<br /><br />session.timeout=120<b