IBM Support

Out Of Memory Errors on the Systemout.log

Troubleshooting


Problem

The system runs out of memory on 64 bit OS when the JvmHeapSize is not adequately set for optimal performance.

Symptom

Example: Errors below from the systemout.log should help in identifying this issue and how to resolve it:

ADME0006W: An exception occurred sending notification javax.management.Notification[source=WebSphere:name=RasLoggingService,process=MXServer,platform=proxy,node=ctgNode01,version=6.1.0.35,type=RasLoggingService,mbeanIdentifier=cells/ctgCell01/nodes/ctgNode01/servers/MXServer/server.xml#RASLoggingService_1228332252827,cell=ctgCell01,spec=1.0][type=websphere.ras.error][message=] to LocalNotificationService: java.lang.OutOfMemoryError
Line 1898: [4/18/11 13:21:13:105 EDT] 00000098 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: ReportBridgeServlet. Exception thrown : java.lang.OutOfMemoryError
Line 2146: java.lang.OutOfMemoryError
Line 2206: [4/18/11 13:21:13:173 EDT] 00000099 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: ReportBridgeServlet. Exception thrown : java.lang.OutOfMemoryError
Line 2417: java.lang.OutOfMemoryError
Line 2684: [4/18/11 13:21:13:274 EDT] 00000098 WebApp E [Servlet Error]-[ReportRequestProcessServlet]: java.lang.OutOfMemoryError

Cause

JvmHeapSize is not set for optimal performance.

Diagnosing The Problem

Locate the systemout.log and search for Property WAS.AppServerJvmHeapMax =
If found with the below example: noticed that it's set to 1024 =1 gb of memory - this is not ideal or advice for an 64 system.

[4/18/11 13:23:11:952 EDT] 00000016 SystemOut O 18 Apr 2011 13:23:11:951 [INFO] BMXAA6450I - Property WAS.AppServerJvmHeapMax = 1024
[4/18/11 13:23:11:952 EDT] 00000016 SystemOut O 18 Apr 2011 13:23:11:952 [INFO] BMXAA6450I - Property WAS.AppServerJvmHeapMin = 512
[4/18/11 13:23:11:953 EDT] 00000016 SystemOut O 18 Apr 2011 13:23:11:952 [INFO] BMXAA6450I - Property WAS.ApplicationServerName = MXServer

Resolving The Problem

Set the JvmHeapSize (on the Application Server) to maximized the 64 bit OS architecture for best performance.

On an 64 bit OS - the setting for the JvmHeapSizeMin should be 1024 and the JvmHeapSizeMax should be set to 2.5 gb.(2560) or more for optimal performance.

Refer to the Maximo v7 performance best practices link below for the edit requirement/suggestions.

Also reference the below URL : Understanding Memory Requirements For 32 And 64 Bit Systems

[{"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Business Unit":{"code":"BU005","label":"IoT"},"Component":"--","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"Version Independent","Edition":"Edition Independent"},{"Product":{"code":"SS6HJK","label":"Tivoli Service Request Manager"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":" ","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"","label":"Windows 2003 server"},{"code":"","label":"Windows 2008 server"}],"Version":"7.2;7.2.1;7.5","Edition":"Edition Independent"},{"Product":{"code":"SSKTXT","label":"Tivoli Change and Configuration Management Database"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":" ","Platform":[{"code":"PF027","label":"Solaris"},{"code":"","label":"Linux Red Hat - iSeries"},{"code":"","label":"Windows 64bit"}],"Version":"7.1.1;7.1.2;7.2;7.2.1;7.2.2;7.5","Edition":"Edition Independent"},{"Product":{"code":"SSLKTY","label":"Tivoli Asset Management for IT"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":" ","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"","label":"Windows 64bit"}],"Version":"7.1.1;7.1.2;7.2;7.2.1;7.2.2;7.5","Edition":"Edition Independent"}]

Document Information

Modified date:
17 June 2018

UID

swg21499074