Naming Service Reported Failed But Never Restarted Properly (Doc ID 2879772.1)

Last updated on JUNE 02, 2024

Applies to:

Symptoms

On : 2.4.0.1.0 version, NMS Infrastructure

Naming Service reported failed but never restarted properly


 

ERROR
-----------------------

System State: CRITICAL - nms:SMService running
System State: CRITICAL - nms:DBService running
System State: CRITICAL - nms:nms-naming-service running
System State: CRITICAL - nms:nms-lighttpd running
System State: CRITICAL - nms:TCDBService running
System State: CRITICAL - nms:MBDBService running
System State: CRITICAL - nms:ODService running
System State: CRITICAL - nms:DDService running
System State: CRITICAL - nms:MTService running
System State: CRITICAL - nms:MBService running
System State: CRITICAL - nms:JMService running
System State: CRITICAL - nms:SwService running
System State: CRITICAL - nms:PFDBService running
System State: CRITICAL - nms:FLMDBService running
System State: CRITICAL - nms:PFService running
System State: CRITICAL - nms:publisher running
System State: CRITICAL - nms:corbagateway running
System State: CRITICAL - nms:TSDBService running
System State: CRITICAL - nms:TSService running
System State: CRITICAL - nms:IVRAdapter running
System State: CRITICAL - nms:ABBRTI running
System State: CRITICAL - nms:ABBServer running
Services NOT Ready - critical services have failed/stopped



and in the managed server log

 ERROR session.CorbaObjectContainer: Unexpected CORBA timeout for InterSys_<intersysname>
org.omg.CORBA.TIMEOUT: Response timed out after: '180000' milliseconds.
        at weblogic.iiop.Utils.mapRemoteToCORBAException(Utils.java:715)

Changes

Cause

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