Hi,
you need to understand where the problem actually is.
Is it in the database or in the JVMs?
If users are logged into multiple JVMs and they are experiencing the problems then it is probably a database level issue.
The JVM logs should give you indications of that.
I blogged about slow SQL log entries to look for here:
http://www.linkedin.com/pulse/individual-bmxaa6720w-slow-sql-entries-maximo-logs-need-mark-robbinsIf an individual JVM is running low on memory then there are likely to be problems with MBOSets not being close.
This article explains how to check which Maximo objects are using a lot of memory:
https://www.linkedin.com/pulse/seeing-which-mbosetsmbos-using-memory-mark-robbins/Other log entries will indicate if the JVM is overloaded and I discuss those in other articles:
https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/If you get really stuck then message me privately, Vetasi offer a log analysis service which dramatically speeds up performance investigations.
My contact details are on my profile details and on connect with me on Linkedin.
------------------------------
Mark Robbins
Support Lead/Technical Design Authority / IBM Champion 2017 & 2018 & 2019 & 2020 & 2021
Vetasi Limited
https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/------------------------------