Slowness in Operations Mobile App (OMA) - Pertaining to Switch Sheets
(Doc ID 2811799.1)
Last updated on OCTOBER 21, 2022
Applies to:
Oracle Utilities Network Management System - Version 2.4.0.1.0 to 2.5.0.1.0 [Release 2.4 to 2.5]Oracle Network Management for Utilities - DMS - Version 2.4.0.1.0 to 2.4.0.1.0 [Release 2.4]
Information in this document applies to any platform.
Symptoms
On : 2.4.0.1.0 version, Web Workspace
When a crew is assigned to a Switch Sheet, the OMA Client runs very slowly
The WebService Call below for example that cause WebLogic to go into hogging threads mode.
POST /nms-ws/trbl-rest/all-events?max_calls=25 200 30563 58.918
POST /nms-ws/trbl-rest/all-events?max_calls=25 200 679968 435.802
POST /nms-ws/trbl-rest/all-events?max_calls=25 200 679968 477.91
GET /nms-ws/mobile/crews/4624/assignments?include-unsent-assignments=true 200 33049 139.314
GET /nms-ws/mobile/crews/4624/assignments?include-unsent-assignments=true 200 33049 103.554
GET /nms-ws/mobile/crews/4624/assignments?include-unsent-assignments=true 200 33049 151.547
This comes from the managed server access.log during testing. This requires extending the logging format as described in this document: Customizing the HTTP access log
Specifically, use the format listed
Expected behavior
Should not get hogging threads occurring when doing basic Switching Sheet operations
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 |
Fix Description |
Migration |
References |