Unable to Start a Managed Weblogic Server that has a Deployment
(Doc ID 1533273.1)
Last updated on APRIL 12, 2024
Applies to:
Oracle Utilities Network Management System - Version 1.12.0 and laterOracle Network Management for Utilities - DMS - Version 1.12.0 and later
Information in this document applies to any platform.
Goal
**Disclaimer:** This KM article may include the following abbreviations:
NMS - Oracle Network Management System
When starting a managed WebLogic server that has a deployment targetted to the managed server, the server fails to start. The state of the server goes to 'RESUMING' forcing the administrator to kill the managed server process and remove the deployment before starting the managed server.
In the managed server log file, the following line is repeated:
2013-01-02 16:26:02,619 [main] ERROR com.splwg.oms.ejb.session.Agent: org.omg.CORBA.COMM_FAILURE: Cound not get naming context vmcid: 0x0 minor code: 0 completed: No
You performed the following steps:
(1) Select deployment and select ‘Force Stop Now’. Select ‘Yes” to stop the Deployments (NOTE: this is the step that is the cause of the issue):
(2) Select the server to stop and select ‘Force Shutdown Now’. Answer “yes’ to forcibly shutdown servers:
(3) Start managed server: Select the server and the 'Start' button. Select ‘Yes’ on the next screen.
At this point the server is in a resuming state and must be killed:
Solution
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
| Goal |
| Solution |
| References |