Skip to main content
Summary Is there a simple way to test if a remote Orbix daemon instance is up and running?
Article Number 13312
Environment All Supported Operating Systems Orbix 3.x Orbix C Runtime Orbix Java Runtime
Question/Problem Description Is there a simple way to test if a remote Orbix daemon instance is up and running?
Given that I don't have Orbix installed on my machine, can I still test if a remote Orbix daemon instance is up and running?
Is there an easy way to verify if a listener socket is active in a remote Orbix process?
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution

Orbix 3.x provides a tool called "pingit" to verify the health status of the Orbix daemon; when this tool is not available, it is possible to run a similar check by using a typical telnet client application.
To do this, open a telnet session directly to the Orbix daemon as follows:

 

%> telnet <HOST WHERE ORBIXD RUNS> <ORBIXD PORT NUMBER>

 

If the Orbix daemon is reachable from that machine you should see
something like:

 

Trying <IP ADRESS/HOSTNAME>...
Connected to <HOSTNAME>.
Escape character is '^]'.

After connecting type the word GIOP and press enter. If the Orbix daemon at the other end is up and running, you should see a message similar to this appear on its output console:

 

[orbixd:New IIOP Connection (<HOSTNAME>:1570) ]

 

However, if for whatever reason the Orbix daemon is not reachable or not listening you'd see something like:

 

Trying <IP ADRESS/HOSTNAME>...
telnet: connect to address <IP ADRESS/HOSTNAME>: Connection refused

Note that this method can also be used to find out if any Orbix server (not just the Orbix daemon) is up an running, all you need to know is the port number where the server is listening for incoming connections and the IP address/hostame where it's deployed.

Workaround
Notes
Attachment
Created date: 06 September 2011
Last Modified: 13 February 2013
Last Published: 23 June 2012
First Published date: 09 September 2011

#Orbix
#KnowledgeDocs