Troubleshooting
Problem
In Maximo, there are two System Properties which deal with timeouts:
mxe.usermonitor.timeout, which has a default value of 30 minutes.
mxe.usermonitor.InactiveSessionTimeLimit, which has a default value of 120 minutes.
In the Maximo directory, there is also a web.xml file located in maximouiweb which has an element session-timeout. The default value is 30 minutes. This file can be found here: SMP\maximo\applications\maximo\maximouiweb\webmodule\WEB-INF
What does each value do? Which value actually determines when a user will receive a timeout during their session?
Resolving The Problem
The property mxe.usermonitor.timeout determines when a user is marked as inactive in the MAXSESSION table. When a user is inactive for the time set in this property, the MAXSESSION record corresponding to this user session will have its "ACTIVE" column set from 1 to 0.
The property mxe.usermonitor.InactiveSessionTimeLimit determines when a user session is actually cleared from the MAXSESSION table. When a user has been inactive for the time set in this property, the MAXSESSION record corresponding to this user will be removed. If Login Tracking is enabled, a SYSLOGOUT record will be added to the LOGINTRACKING table for that user account.
This means the mxe.usermonitor.InactiveSessionTimeLimit should always be greater than the value of mxe.usermonitor.timeout.
However, neither properties determine when a front-end user will actually see a timeout in their browser. This is solely determined by the session-timeout element in the web.xml file. When a user reaches the value set in the web.xml, they will receive a message in their browser explaining they have been timed out and must log back in. If Login Tracking is enabled, a TIMEOUT record will be added to the LOGINTRACKING table for that user account.
However, neither properties determine when a front-end user will actually see a timeout in their browser. This is solely determined by the session-timeout element in the web.xml file. When a user reaches the value set in the web.xml, they will receive a message in their browser explaining they have been timed out and must log back in. If Login Tracking is enabled, a TIMEOUT record will be added to the LOGINTRACKING table for that user account.
To summarize, the usermonitor properties only determine the status of the user entry in the MAXSESSION table. The session-timeout element is what actually determines when a user will experience a timeout in their browser.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"System Related","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2019
UID
swg21670962