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

Last updated on JUNE 15, 2017

Applies to:

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

Goal

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 adminstrator 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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms