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 23, 2018

Applies to:

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

Symptoms

On : 1.12.0.3 version, Java Application Server

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

Starting with 1.12.0.3.33, 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...
  successful.
Attempting to resolve InterSys_nms
org.omg.CosNaming.NamingContextPackage.NotFound
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
NameService=corbaloc:iiop:1.2@nms-server1:17830/NameService
Testing corba name service port
Testing port NamingService
Resolving host: nms-server1
  Resolved to nms-server1/[IP ADDRESS]
Testing socket on port 17830
com.splwg.oms.ejb.ConfigException: NamingService is not listening on port 17,830 on nms-server1. Verify that the correct port is configured
  at com.splwg.oms.ejb.TestGatewayConfig.testPort(TestGatewayConfig.java:325)
...
Security tests failed. Aborting

 

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


Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.