On Thursday 15 July, "yateen joshi" wrote:
> We are testing a simple application for interoperability.
> During that, we get following error -
> C:\Documents and
> Settings\rkakar.NULINKIND>C:\omni\bin\x86_win32\catior.exe -o
> IOR:010000001d00000049444c3a546573742f53657373696f6e5f436f6e747
> 26f6c3a312e300000000001000000000000007000000001010200130000006b
> 726973686e612e6e756c696e6b2e636f6d0000cdd200001b00000014010f005
> 25354b127f640dd980b00000000000100000001000000000200000000000000
> 0800000001000000004f41540100000014000000011e1f08010001000000000
> 00901010000000000
>
> Type ID: "IDL:Test/Session_Control:1.0"
> Profiles:
> 1. IIOP 1.2 my_server:911420 Object key not recognised as from omniORB.
>
> Does this mean that OmniORB client "cannot communicate" with this
> server.
That is not the output of the catior command you have given above, or
indeed catior with any options. The "Object key not recognised as from
omniORB" is due to specifying the -o option when the IOR is not from
omniORB. -o tries to tell you more about what an omniORB object key
means, which it obviously can't do if the IOR didn't come from
omniORB. Miss out the -o and it will show you the key properly.
Also, catior does not report host / port with a colon, and 911420 is
not a valid port number. 911420 could not have possibly been the
number stored in an IOR since IORs store port numbers in a 16 bit
value.
What have you really done? When I run catior on that IOR, I see this:
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 is a perfectly valid IOR, and omniORB will talk to it fine. The
object reference came from TAO.
> If No, then what is the meaning of this exception.
>
> Caught Exception: omniORB.CORBA.TRANSIENT Minor:
> TRANSIENT_ConnectFailed, COMPLETED_NO.
That means the server was not listening on the port specified in the
IOR. omniORB didn't even get as far as trying to talk to it. Make sure
the server is running, and you have an up to date IOR for it.
Cheers,
Duncan.
--
-- Duncan Grisby --
-- duncan at grisby.org --
-- http://www.grisby.org --