Maximo

 View Only
Expand all | Collapse all

mxe.usermonitor.InactiveSessionTimeLimit

  • 1.  mxe.usermonitor.InactiveSessionTimeLimit

    Posted Fri March 14, 2025 08:30 AM

    Hi everyone,

    Where can I change value of this mxe.usermonitor.InactiveSessionTimeLimit. When I go trough Maximo, value field is readonly, and I can not find it in web.xml. I need to increase this value.

    Thank you



    ------------------------------
    Dario Stjepanović
    ------------------------------


  • 2.  RE: mxe.usermonitor.InactiveSessionTimeLimit

    Posted Mon March 17, 2025 04:38 AM

    Hi Dario,

    For readonly properties it's still possible to update them directly in the database. In your case it should be like this (change the value to the desired time limit):

    UPDATE MAXPROPVALUE
    SET PROPVALUE = '180'
    WHERE PROPNAME = 'mxe.usermonitor.InactiveSessionTimeLimit';

    When changing this way you will have to restart Maximo server to apply the change.

    Please note that this value should be aligned with the Maximo session timeout, read more here: https://www.ibm.com/support/pages/understanding-maximo-timeout-values-webxml-session-timeout-and-usermonitor



    ------------------------------
    Ivan Lagunov
    Head of R&D
    ZNAPZ B.V.
    ------------------------------



  • 3.  RE: mxe.usermonitor.InactiveSessionTimeLimit

    Posted Mon March 17, 2025 10:40 AM

    We just did this, and waiting for confirmation from our client.

    Thank You for your help.



    ------------------------------
    Dario Stjepanović
    ------------------------------



  • 4.  RE: mxe.usermonitor.InactiveSessionTimeLimit

    Posted Mon March 17, 2025 09:58 AM
    Edited by Tinnokesh AP Mon March 17, 2025 10:09 AM

    Hello Dario,

    You would be able to change through maximo.properties file



    ------------------------------
    Tinnokesh AP
    ------------------------------



  • 5.  RE: mxe.usermonitor.InactiveSessionTimeLimit

    Posted Tue March 18, 2025 05:05 PM
    Edited by Aiman Ansari Tue March 18, 2025 05:05 PM
    Hi Dario,
    The property mxe.usermonitor.InactiveSessionTimeLimit determines when a user session is cleared from the MAXSESSION table. 
    There are two system properties which deal with timeouts: mxe.usermonitor.timeout and mxe.usermonitor.InactiveSessionTimeLimit.
    However, neither of these determine when a front-end user will actually see a timeout in their browser. This is defined in the web.xml file in session-timeout element (defaulted to 30 mins).
    For more details, please refer this link: 
    https://www.ibm.com/support/pages/understanding-maximo-timeout-values-webxml-session-timeout-and-usermonitor
     
    Regards,
    Aiman


    ------------------------------
    Aiman Ansari
    Maximo Consultant
    ZNAPZ B.V.
    Breda
    ------------------------------



  • 6.  RE: mxe.usermonitor.InactiveSessionTimeLimit

    Posted Wed March 19, 2025 04:26 AM

    Hi Aiman,

    We already did that, we changed value in web.xml.

    Our problem is, after some time of not working in IBM Maximo, client is still logged in application, but IBM  Maximo is not working. For example, if someone work in workorder application and if he is on first tab of wotrack application, if he try to switch to another tab he can not do that, if he fill values on that first tab he can not save that value. Client fill value on first tab, and want to save he can not, because application is not responding, looks like application is freezing, if You can understand me. 

    Can this be because of web browser or do I need setup something else in Maximo application.



    ------------------------------
    Dario Stjepanović
    ------------------------------



  • 7.  RE: mxe.usermonitor.InactiveSessionTimeLimit

    Posted Wed March 19, 2025 05:13 AM
    Edited by Ivan Lagunov Wed March 19, 2025 05:13 AM

    Hi Dario,

    First, it's important to note the Maximo version you're using. The earlier advice regarding web.xml applies to Maximo 7.6. In MAS 8/9, you can modify the "Session idle timeout" via the MAS administration UI: https://www.ibm.com/docs/en/masv-and-l/continuous-delivery?topic=administering-licenses-apppoints-usage#idle_session__title__1

    1. From the Suite administration page, select license consumption.
    2. On the Configuration tab, enable Idle timeout.
    3. Specify the length of time a session can be idle before that session is automatically logged out.
    4. Save your changes.

    We experienced a similar issue in MAS 8 when a user kept a browser tab open, leading to MAS session expiration. There is a UX issue in Manage related to this, as the user is not always informed of the session expiration. For example, if data is already filled on the page and the session expires, clicking a button (e.g., to save or switch tabs) won't notify the user of the expiration. In our case, the user received a confusing server error message. By examining the web server logs (specifically the error and access logs), we traced the issue to the HTTP call to /maximo/ui/maximo.jsp, which occurs on button clicks. The request was redirected to the MAS login page, indicating session expiration. This differs from your description of application freezing.

    I recommend using the browser's developer tools network panel to analyze HTTP requests when this occurs. If direct analysis is not possible and the issue only happens for the customer, check the web server logs to identify the root cause.

    I hope this helps resolve the issue. Please let me know if you have any further questions.



    ------------------------------
    Ivan Lagunov
    Head of R&D
    ZNAPZ B.V.
    ------------------------------



  • 8.  RE: mxe.usermonitor.InactiveSessionTimeLimit

    Posted Wed March 19, 2025 07:19 AM

    Hi Ivan,

    We are using IBM Maximo Asset Management 7.6.1.3.

    Thank You for your suggestions.



    ------------------------------
    Dario Stjepanović
    ------------------------------



  • 9.  RE: mxe.usermonitor.InactiveSessionTimeLimit

    Posted Thu March 20, 2025 04:33 AM

    Hi,

    I found this solution and we will try it, did anyone already try this:

    https://www.ibm.com/support/pages/maximo-browser-session-freezes-randomly-when-application-security-enabled



    ------------------------------
    Dario Stjepanović
    ------------------------------



  • 10.  RE: mxe.usermonitor.InactiveSessionTimeLimit

    Posted Thu March 20, 2025 10:54 AM

    Hi Dario,

    1. The link here - https://www.ibm.com/support/pages/maximo-browser-session-freezes-randomly-when-application-security-enabled mentions some sample error in logs. Are you able to see any of these errors in logs?
    2. If no errors are seen in step 1, checking the browser site settings to disable cache might help.
    As Ivan suggested earlier, analysing the developer tools and web server logs could give you more insights on the issue as well.

    Please let me know in case of any further questions.

    Regards,

    Aiman



    ------------------------------
    Aiman Ansari
    Maximo Consultant
    ZNAPZ B.V.
    Breda
    ------------------------------



  • 11.  RE: mxe.usermonitor.InactiveSessionTimeLimit

    Posted Fri March 21, 2025 08:50 AM

    If this is what it sounds like, I've seen this issue in 7.x for as long as I can remember. What I found is Maximo is only tracking activity on one session when a user has multiple going. If you check the MAXSESSION table while having multiple sessions going and test making updates, you should see that the "lastactivity" is only getting updated for one of them.  If a user starts working in one session consistently and it's not the one where activity is getting updated, their other session will eventually time out which will cause all of the sessions to end and the user will end up with a surprise logout.

    The only out-of-the-box solution I've been aware of is to either not allow multiple sessions or boost the timeout dramatically in the web.xml.



    ------------------------------
    Brandon Fisher
    ------------------------------