Apliqo tomcat server time-out fixed at 30 min
Issue #314
resolved
The Apliqo web server time-out appear to be fixed at 30 minutes (i.e., clients are logged out of the webapp after 30 min of inactivity). This is related to the issue I had put on the forums and it is not specific to authentication mode and cannot be increased or decreased regardless of any of the time-out parameters: https://forum.cubewise.com/t/ux-time-out-with-cam/4282/9
I suspect this is Tomcat issue (and made its way to Apliqo in once of the recent releases when the Tomcat server was updated) but there is more information in the forum post I had linked.
Comments (5)
-
-
I found a solution for an old Apliqo version: 2.5.2.2. If it works or not for you, please, continue discussion under Wei Wang’s original post: https://forum.cubewise.com/t/ux-time-out-with-cam/4282/10, to not to keep two conversations in two spaces.
-
+1 - this solution in the forum link above resolved our issue for time outs too.
-
- changed status to resolved
New section on setting session timeout has been added to the documentation:
-
- removed milestone
Removing milestone: 2020_Q4 (automated comment)
- Log in to comment
We are seeing the same behavior after upgrading from v2021.02 to 2021.07. Previously, we had UX, CAM/TM1/PAW all set to a 4 hour timeout, which was working well. After upgrading, we saw that the web.xml file was overwritten back to default 30mins. Even after changing that back to 240m, we are still seeing UX time out after 30 mins of inactivity. As part of the 2021.07 upgrade process, we did leave the box checked to upgrade the web server component. This is a usability issue for us because users ideally don’t want to be logging all the time if they step away from their desks.