My Oracle Support Banner

Unable to Start a Managed Weblogic Server that has a Deployment (Doc ID 1533273.1)

Last updated on MARCH 01, 2019

Applies to:

Oracle Utilities Network Management System - Version 1.10.0 and later
Oracle Network Management for Utilities - DMS - Version 1.10.0 and later
Information in this document applies to any platform.

Goal

**Examples provided in this article do not represent real life personal/confidential information**

**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:00,618 [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
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

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.