Occasionally, Maximo
became unavailable for a short period of 5-10 minutes. Alarms were raised, IT
help desk was called, and the issue got escalated to the Maximo specialist
(you). You logged into the server, checked the log file, and found a Java
Out-of-Memory (OOM) issue. Not a big deal, the server usually restarted itself
and became available soon after that. You reported back to the business and
closed the issue. Does that scenario sound familiar to you?
If such an issue has
only occurred to your system once, it was probably treated as a simple problem.
But since you had to search for a solution on the web and ended up here,
reading this article, probably it has occurred more than once, the business
requires it to be treated as a critical incident. As the Maximo specialist,
you’ll need to dig deeper to report the root cause of the issue and provide a
fix to prevent it from occurring again. Analyzing low level Java issue is not
an easy task, and this post describes my process to deal with this issue.
