Maximo

 View Only

 Maximo Anywhere Opens Hundreds of Sessions Each Time a User Logs In

  • IBM Maximo
  • Maximo
  • Maximo Anywhere
osama attia's profile image
osama attia posted 07/08/26 06:47 AM

Hello everyone,

We have had Maximo Anywhere in our environment for quite a while, but we only started using it actively recently.

We noticed that the number of active login sessions generated by Anywhere logins is extremely high. A single user login can create hundreds of active sessions.

From our observations, this seems to happen mainly while lookups and other reference data are being downloaded to the device.

We searched online and found several discussions describing this as a side effect of using SSO or running older product versions. However, neither of those apply to our environment:

  • Tivoli Process Automation Engine: 7.6.1.2 IFIX20220330

  • IBM Maximo Asset Management Work Centers: 7.6.0.4

  • IBM Maximo Anywhere: 7.6.4.0

  • IBM TPAE Integration Framework: 7.6.1.2

  • TPAE OSLC Object Structure: 7.6.4.0

Has anyone experienced this behavior before? If so, were you able to identify the root cause or find a solution?

Any help or suggestions would be greatly appreciated.

Thank you!

#IBMMaximo #MaximoAnywhere #Maximo

Bartosz Marchewka's profile image
Bartosz Marchewka IBM Champions

Hi @osama attia

I think this is known product defect and was fixed in Maximo Anywhere 7.6.4 IFIX2

IJ33311 - LOGIN USING LATEST ANYWHERE 7.6.4 APPS FROM IOS APPSTORE RESULTS IN MULTIPLE ENTRIES IN MAXSESSION & LOGINTRACKING

Which IFIX version for Anywhere 7.6.4 was installed in the environment that you mentioned?

FYI The latest available is IFIX6.

osama attia's profile image
osama attia

Hello @Bartosz Marchewka 
Thanks for your answer 
Yes, we are one IFIX2 
TPAE OSLC Object Structure 7.6.4.0 Build 20211126_150850-0500 DB Build V7640-07

Bartosz Marchewka's profile image
Bartosz Marchewka IBM Champions

Thanks for confirming, Osama. Since you're on IFIX2 and the latest available is IFIX6, my suggestion would be to upgrade to IFIX6 and then try to reproduce the issue again in a NON-PROD environment. If the behaviour persists, it's worth opening an IBM support case at that point - but IBM will very likely ask you to first apply the latest IFIX and confirm whether the problem still occurs before they proceed with troubleshooting, so doing that upfront should save you a round trip.

osama attia's profile image
osama attia

@Bartosz Marchewka
we have done the latest IFIX
unfortunately, still the same problem 
I don't think IBM still allows to open cases for Maximo 7.6 or do they still accept it?

Bartosz Marchewka's profile image
Bartosz Marchewka IBM Champions

Hi @osama attia

Thank you for sharing that information. It's not good that the problem still exists.

Regarding IBM cases for Anywhere 7.6.4 when we last opened one three weeks ago, they responded: "Support for Maximo Anywhere remains available under Extended Support; bug fixes are only for critical issues". So the question is whether this qualifies as a critical issue. In my opinion, it's worth registering a case and seeing how IBM classifies it.

Mark Robbins's profile image
Mark Robbins IBM Champions

@Bartosz Marchewka said this:

""Support for Maximo Anywhere remains available under Extended Support; bug fixes are only for critical issues"

So the question is whether this qualifies as a critical issue. In my opinion, it's worth registering a case and seeing how IBM classifies it."

Just a thought... IBM Extended Support is an add-on, paid support option... on top the standard annual Subscription and Support (S&S) renewal fee

Be aware that IBM Support may not even discuss this problem in detail with you unless you have extended support. I suspect that they would want more information and to an investigation and that extra work would be covered by extended support.

Mark Robbins's profile image
Mark Robbins IBM Champions

@osama attia - have you checked to see if the database connection counts rise and fall with these requests?

Try setting the dbconnection logger to WARN and seeing if the DB connection watchdog starts reporting lots of leaked connections. 

I discuss sample log messages in this article: https://www.linkedin.com/pulse/db-connections-mbosets-understanding-which-piece-code-mark-robbins/

There is a small possibility that the Anywhere code is triggering some code that isn't closing the connections, although this wouldn't normally keep sessions open.

In my experience switching the logger to WARN would have a minimal performance impact on the system but it can help uncover really serious resource leak issues.

If you do get lots of "DbConnectionWatchDog:Db Connection open:" messages that you don't know how to interpret then feel free to reach out to me privately and I can glance at them.

Bartosz Marchewka's profile image
Bartosz Marchewka IBM Champions

Hi @Mark Robbins

FYI The support is also available when you are in "IBM Maximo Asset Management Dual Support".

osama attia's profile image
osama attia

@Mark Robbins
the DBconnection did not get affected