Weblogic Managed Server Start Order Should not be Important for Flex and OMA
(Doc ID 2853345.1)
Last updated on MAY 31, 2024
Applies to:
Oracle Utilities Network Management System - Version 2.5.0.1.0 to 2.5.0.1.0 [Release 2.5]Oracle Network Management for Utilities - DMS - Version 2.5.0.1.0 to 2.5.0.1.0 [Release 2.5]
Information in this document applies to any platform.
Symptoms
On : 2.5.0.1.0 version
When running two weblogic instances to support separation of the NMS-WS adapter and Core NMS, Weblogic manage server start order is important for Flex and OMA
The Flex managed server always has to be started and running before the NMS managed server running CESEJB can be started. This should not be the case. The managed servers should be able to start in any order.
Steps:
Stop managed server running NMS-WS adapter (Flex) in its weblogic instance
Stop managed server running CESEJB (core nms) in its weblogic instance
Start managed server running NMS-WS adapter (Flex or OMA) in its weblogic instance
Start managed server running CESEJB (core nms) in its weblogic instance
If this is done out of order, this error is produced when trying to log into Flex or OMA
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 |
Cause |
Solution |
Fix Description |
Migration |
References |