Corba.Comm_failure When Attempting to Access NMS Application
(Doc ID 1318075.1)
Last updated on APRIL 12, 2024
Applies to:
Oracle Utilities Network Management System - Version 1.9.0 and laterOracle Network Management for Utilities - DMS - Version 1.9.0 and later
Information in this document applies to any platform.
Symptoms
When trying to start the NMS applications, a dialog appears indicating a CORBA.COMM_FAILURE: Could not resolve object name
- OR -
this appears in the managed server log:
Testing corba name service port
Testing port NamingService
Resolving host: omsvm1new
Resolved to <SERVER 1>/###.###.###.###
Testing socket on port 17820
successful.
Attempting to narrow...
successful.
Attempting to resolve InterSys_nmsadmin
successful.
Testing port InterSys_nmsadmin
Resolving host: omsvm1new
Resolved to <SERVER 1>/###.###.###.###
Testing socket on port 30938
2016-10-27 18:36:13,161 [main] ERROR com.splwg.oms.ejb.session.Agent: TestGatewayConfig failed
com.splwg.oms.ejb.ConfigException: Unexpected Error: java.net.NoRouteToHostException: No route to host
at com.splwg.oms.ejb.TestGatewayConfig.test(TestGatewayConfig.java:128)
Changes
The server experiencing this is a new installation of NMS. Other servers have been set up on the same subnet that are not having any issues.
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! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |