Maximo

What leads a session getting expired immediately after login and keep happening again and again? Sometimes we need to take http server restart.

Selena

There are probably errors being generated in System.Out or SystemErr logs files to at least give a path to investigate it.

It could be a problem with your sessions not getting cleared and therefore the new session being terminated.

You might also want to check your MAXSESSION table to see if there are lots of sessions not being cleared correctly. I would also check System Properties for:
mxe.usermonitor.timeout (this is how long after the user is inactive that they're logged out)

mxe.usermonitor.InactiveSessionTimeLimit (this shouldn't be too high as it will leave invalid sessions in the maxsession table, 120 is the default but it must be greater than the value of the property above).

mxe.webclient.maxUISessionsPerHttpSession (This defaults to 10, it shouldn't be too low as the user's old session may still be in the table even though it's inactive which could cause the system to not let a new session be created)

mxe.webclient.maxuisessions (this is the maximum for the server, 0 is unlimited and that's the default)

Helen Fisher

Marketing Manager at BPD Zenith

Happy to be contacted at: helen.fisher@bpdzenith.com

The session manager uses cookies to store the session ID on the client between requests.  Something might be awry with "session tracking".  To debug, try walking through steps in HTTP sessions are not getting created, or are lost between requests.

Hello Selena,

You don't say anything about your environment but presumably it has multiple JVMs and a load balancer in front of them.

If so then you could well be being hit by a session affinity problem as Michael refers to.

"The session manager uses cookies to store the session ID on the client between requests.  Something might be awry with "session tracking".  To debug, try walking through steps in HTTP sessions are not getting created, or are lost between requests."

In that situation the requests from the client PC could be being directed to JVMs othen than the JVM that the user is actually logged into. The other JVMs will receive the requests and realise that it isn't for them and log the user out.

You can check which JVMs are being receiving the requests by checking the web server logs (assuming you are using the IBM HTTP server). You may need to configure the access.log file further, if you need help with the configuration then reach out to me and I can provide some additional information on what to configure.

best regards,

Mark

For my advice on how to make Maximo easier to support visit my blog and webexes here:

https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins?published=t

It might be the system is stuck in Admin mode which results an immediate logout for non-admin users and/or the allowed number users are in this mode are set to 1.