Deployments Are Not Coming Up When a Managed Server Migrates To a Back Up Machine In a Cluster.
(Doc ID 1912814.1)
Last updated on FEBRUARY 23, 2024
Applies to:
Oracle Communications Order and Service Management - Version 7.2.0 to 7.2.2 [Release 7.2]Information in this document applies to any platform.
Symptoms
On : 7.2.0 version, with Clustering
Deployments are Not coming up when a managed server migrates to a back up machine in a cluster.
Customer installed OSM 7.2.0.9 on WeLogic active active cluster.
They have 2 machines with 1 managed server running in each.
When MS1 which is running on machine 1 migrates to machine 2, deployments are not coming and we are receiving the following error. Same issue happens in the reverse order.
ERROR
-----------------------
weblogic.management.DeploymentException: [J2EE:160204]The ApplicationLifecycleListener 'com.mslv.oms.j2ee.LifecycleListener' of application 'oms' has a run-as user configured with the principal name 'oms-internal' but a principal of that name could not be found. Please ensure a user with that name exists.
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 |