My Oracle Support Banner

NMS Client Out Of Memory (Doc ID 2434717.1)

Last updated on MARCH 10, 2019

Applies to:

Oracle Utilities Network Management System - Version 2.3.0.0.0 to 2.3.0.2.0 [Release 2.3]
Oracle Network Management for Utilities - DMS - Version 2.3.0.0.0 to 2.3.0.2.0 [Release 2.3]
Information in this document applies to any platform.

Symptoms

**Any examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:

NMS - Oracle Network Management System
JRE - Java Runtime Environment

On : 2.3.0.1.0 version, Java Application Server

ACTUAL BEHAVIOR
---------------
NMS Client out of Memory

1200MB allocate to the 64bit versions of the JRE running on the NMS Client. However the client ran out of memory after being logged in for few hours.


"2018-08-02 13:59:44,045 [AWT-EventQueue-1] ERROR com.splwg.oms.jbot.DefaultDataStore: SwmanSafetyDataStore.resetStudySession - Save safety document's study values failed:
com.splwg.oms.framework.exception.OmsServiceException: Exception [EclipseLink-5010] (Eclipse Persistence Services - 2.6.5.v20170607-b3d05bd): org.eclipse.persistence.exceptions.OptimisticLockException
Exception Description: The object [com.splwg.oms.model.entity.safety.SafetyDocument@9a426] cannot be merged because it has changed or been deleted since it was last read.
Exception in thread "AWT-EventQueue-1" java.lang.OutOfMemoryError: Java heap space"


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.