My Oracle Support Banner

JMService Consumes an Enourmous Amount of Additional Memory During Normal Usage (Doc ID 2117860.1)

Last updated on MARCH 26, 2019

Applies to:

Oracle Utilities Network Management System - Version 1.11.0.4 to 1.12.0.3 [Release 1.11 to 1.12]
Oracle Network Management for Utilities - DMS - Version 1.11.0.4 to 1.12.0.3 [Release 1.11 to 1.12]
Information in this document applies to any platform.

Symptoms

JMService consumes an ever increasing amount of memory.

Running 'Action any.JMService dump memstats' shows that JMJobManager is the culprit:


JMJobManager [
  completedJobList.size() = 7075
  job_by_alarm.size() = 7151
  job_by_event.size() = 7151
  jobs_by_device.size() = 76
  jobs_by_sheet.size() = 0
  calls_by_xid.size() = 137387
  calls_by_intr.size() = 0
  troubleFeeders.length() = 19
  momentaryFeeder.getJobs().size() = 0
  total # jobs by device = 76
  total # jobs by sheet = 0
  total # calls by xid = 2270526
  total # calls by intersection = 0
  total # jobs in troubleFeeders = 113
  total distinct JMJob instances = 7158
  total distinct JMCall instances = 2270598
  bytes used by JMJob instances = 178922432
  bytes used by JMCall instances = 5526416893
]
 

This can be reproduced (and is caused) by loading a large number of completed jobs using the "Load Completed Events - Range..." option in WorkAgenda and specifying a large date range.

Have the same or a different user repeat the "Load Completed Events - Range..." action specifying the same range.   The number of JMCalls JMService has in memory will increase.

 

 

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.