| Summary | Orbix client fails to start up and connect to Configuration Repository |
|---|---|
| Article Number | 16282 |
| Environment | Orbix 6.x All Supported Operating Systems |
| Question/Problem Description | Orbix client fails to start up and connect to Configuration Repository
E - exception while initializing orb: org.omg.CORBA.INITIALIZE: Failed to narrow CFR reference vmcid: 0x0 minor code: 0 completed: No
CORBA System Exception: org.omg.CORBA.INITIALIZE: Failed to narrow CFR reference vmcid: 0x0 minor code: 0 completed: No (missing subsystem:missing name) |
| Clarifying Information | |
| Error Message | Turning the log level to maximum by setting event_log:filters=["*=*"] shows W - could not lookup database info for host 'xyz' - exception: name resolution failure: java.net.UnknownHostException: xyz |
| Defect/Enhancement Number | |
| Cause | This is caused by failing to lookup the unqualified hostname of the machine running the Configuration Repository. The IOR of the CFR contains the unqualified hostname. |
| Resolution | Ensure the IOR of the CFR contains the fully qualified hostname and the hostname is valid. In order to generate IORs containing the fully qualified hostname, when creating an Orbix domain itconfigure needs to be run in expert mode. Just cancel the creation of a new domain right after the start of itconfigure and then select File->New->Expert. On the first screen were the "Domain Details" can be configured, the "Address Mode Policy for Object References" needs to be set to "fully qualified hostname". This will ensure the IORs will contain the fully qualified hostname. |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 06 September 2011 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 26 June 2012 |
| First Published date: | 10 September 2011 |
#KnowledgeDocs
#Orbix
