"com.splwg.oms.ejb.ConfigException: NamingService Is Not Listening On Port 17,820 On [server]" Error
(Doc ID 2370519.1)
Last updated on DECEMBER 09, 2021
Applies to:
Oracle Utilities Network Management System - Version 2.3.0.0.0 and laterOracle Network Management for Utilities - DMS - Version 2.3.0.0.0 and later
Information in this document applies to any platform.
Symptoms
"com.splwg.oms.ejb.ConfigException: NamingService is not listening on port 17,820 on [server]" Error
Continuation of SR 3-16705353791
When starting the managed server, these errors appear in the log file:
ERROR
-----------------------
Testing WebLogic version
Ear version: 12.2.1.0.0
Server version: 12.2.1.0.0
Testing the following initial reference
NameService=corbaloc:iiop:1.2@NMS-SERVER1:17820/NameService
Testing corba name service port
Testing port NamingService
Resolving host: NMS-SERVER1
Resolved to NMS-SERVER1/127.0.1.1
Testing socket on port 17820
2018-01-29 08:24:07,641 ERROR session.Agent:171 - TestGatewayConfig failed
com.splwg.oms.ejb.ConfigException: NamingService is not listening on port 17,820 on NMS-SERVER1. Verify that the correct port is configured
at com.splwg.oms.ejb.TestGatewayConfig.testPort(TestGatewayConfig.java:289)
...
2018-01-29 08:24:07,653 INFO session.CorbaObjectContainer:235 - ORB: weblogic.corba.orb.ORB
2018-01-29 08:24:07,684 WARN session.CorbaObjectContainer:309 - Could not set naming context: NameService=corbaloc:iiop:1.2@NMS-SERVER1:17820/NameService
org.omg.CORBA.COMM_FAILURE: Connection refused vmcid: 0x0 minor code: 0 completed: No
at weblogic.iiop.Utils.mapToCORBAException(Utils.java:885)
at weblogic.iiop.IORManager.locateNameService(IORManager.java:157)
Changes
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 |