My Oracle Support Banner

If NamingService Is Not Running, With P33, The Managed Server Now Actually Aborts On Startup (Doc ID 2377249.1)

Last updated on MARCH 21, 2019

Applies to:

Oracle Utilities Network Management System - Version to [Release 1.12 to 2.3]
Oracle Network Management for Utilities - DMS - Version to [Release 1.12 to 2.3]
Information in this document applies to any platform.


On : version, Java Application Server

If NamingService is not running, the Managed Server exits on startup, rather than waiting.

Starting with, if the Corba gateway was not running when the managed server was started, the Managed Server would log a message and pause until it detected the corbagateway.

Corba gateway is not ready... retrying...
Attempting to narrow...
Attempting to resolve InterSys_nms
Corba gateway is not ready... retrying...

However, if NamingService is not running (e.g. all services are down with an sms_stop.ces -aS), then the Managed Server now actually aborts and shuts down:

Testing the following initial reference
Testing corba name service port
Testing port NamingService
Resolving host: <NMS SERVER>
  Resolved to <NMS SERVER>/[IP ADDRESS]
Testing socket on port <NMS_NS_PORT>
com.splwg.oms.ejb.ConfigException: NamingService is not listening on port<NMS_NS_PORT> on <NMS_NS_HOST>. Verify that the correct port is configured
  at com.splwg.oms.ejb.TestGatewayConfig.testPort(
Security tests failed. Aborting


It is expected that the Managed Server should wait until the needed services become available.


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

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