[omniORB] OmniORB doubts

Alex Tingle alex.tingle at bronermetals.com
Thu Jul 15 11:27:10 BST 2004


Hello,

> >catior.exe  -o
> IOR:0100000...00000
> Type ID: "IDL:Test/Session_Control:1.0"
> Profiles:
> 1.	IIOP 1.2 my_server:911420 Object key not recognised as from
> omniORB.

You should only use the -o option if the IOR was generated by omniORB. 
Without the -o, your IOR gives:

Type ID: "IDL:Test/Session_Control:1.0"
Profiles:
1. IIOP 1.2 krishna.nulink.com 53965 "....RST.'. at ................"
             TAG_ORB_TYPE 0x54414f00
             TAG_CODE_SETS char native code set: ISO-8859-1
                           char conversion code set:
                           wchar native code set: UTF-16
                           wchar conversion code set:

That looks OK to me. The server is on krishna.nulink.com, port 53965.

> Does this mean that OmniORB client "cannot communicate" with this
> server.

An omniORB client should be able to communicate with any CORBA server. 
Your server seems to be using TAO, which is known to work with omniORB.

> If No, then what is the meaning of this exception.
>
> Caught Exception: omniORB.CORBA.TRANSIENT Minor:
> TRANSIENT_ConnectFailed, COMPLETED_NO.

Probably means that your server is inaccessible, or inactive. Can you 
connect to it using telnet? Try:

  % telnet krishna.nulink.com 53965

If that fails with a message like "connection failed" then your server 
isn't listening on the port listed in the IOR.

It looks like your server is taking a random port each time it starts. 
You realise that this means you need a new IOR each time?

> We are facing a major problem in determining the interoperability of
> Omni ORB.
> So please clarify the things for us.

Hope that helps.

-Alex Tingle

--
Dammit Jim, I'm a programmer... not a mind reader!
On 15 Jul 2004, at 08:02, yateen joshi wrote:




More information about the omniORB-list mailing list