NMS Client Locked Up for About 10 Minutes Or More After AMR Pinging Large Number of Meters
(Doc ID 2210689.1)
Last updated on MARCH 21, 2019
Applies to:Oracle Network Management for Utilities - DMS - Version 18.104.22.168 to 22.214.171.124.0 [Release 1.11 to 2.3]
Oracle Utilities Network Management System - Version 126.96.36.199 to 188.8.131.52.0 [Release 1.11 to 2.3]
Information in this document applies to any platform.
**Examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:
AMR - Automatic Meter Reading
NMS - Oracle Network Management System
AMI - Automated Meter Information
CPU - Central Processing Unit
JVM - Java Virtual Machine
NMS Client locked up for about 10 minutes or more after AMR Pinging 282 meters. Screens wouldn't redraw, couldn't select anything in WorkAgenda, etc.
AMI Pings were just implemented.
Pinging a single meter works fine.
Jconsole showing multiple messages like:
2016-12-01 13:40:08,817 [pool-2-thread-15] WARN com.splwg.oms.client.util.proxy.ProxyInvocationHandler: invoke: ITroubleInfoBean.getCustomersForDevice elapsed: 77410 ms. req: 262 bytes, resp: 443407 bytes
After about 10 minutes, NMS client was working again.
Brought up JConsole on the client. Tried pinging another large batch, about 230 meters.
No indication of extreme CPU or Memory utilization there either. JVM can grow to 2G, but was only using about 1G.
How to Repeat
On a system with large number of records in the AMR_RESPONSES table select a device which has AMI customers in the Viewer and open the AMI Customers page.
Note to long it takes to populate the list of AMI customers for the device.
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