[omniORB] An OmniORB question : connecting to remote object (server)

Amit Lodh alodh@houston.geoquest.slb.com
Tue, 03 Apr 2001 15:47:18 -0500


Hi,

I would really appreciate if somone can help me with the following.

I am running my server and client applications on linux machines (both
running redhat linux) on two subnets with omniORB(installed and
configred identically, using python 1.5.2) running them.

I start the server in one host (one one subnet).

I run the client with the IOR in the command line (on another subnet).
Client dies saying 'Abort'. Do I need to do something additional in
order to use remote server objects?

The IOR
IOR:010000001200000049444c3a436f6d706f6e656e743a312e3000000001000000000000002a000000010100000c0000003139322e3136382e312e3500bf1100000e000000fe5133ca3a00005bc40000000000

, when parsed on ILU parser, gives the following result :

_IIOP_ParseCDR:  byte order LittleEndian, repository id
<IDL:Component:1.0>, 1 profile
_IIOP_ParseCDR:  profile 1 is 42 bytes, tag 0 (INTERNET), LittleEndian
byte order
(iiop.c:parse_IIOP_Profile):  bo=LittleEndian, version=1.0,
hostname=192.168.1.5, port=4543, object_key=<.Q3.:..[......>
(iiop.c:parse_IIOP_Profile):  encoded object key is
<þQ3Ê%3A%00%00%5BÄ%00%00%00%00%00>
(iiop.c:parse_IIOP_Profile):  non-native cinfo is
<iiop_1_0_1_þQ3Ê%253A%2500%2500%255BÄ%2500%2500%2500%2500%2500@tcp_192.168.1.5_4543>
object key is <#FEQ3#CA:#00#00[#C4#00#00#00#00#00>;
 no trustworthy most-specific-type info; unrecognized ORB;
 reachable with IIOP 1.0 at host "192.168.1.5", port 4543

I will really appreciate any help.

Thanks,
Amit

ps : my client code and server code resmbles the code given in the
'echo' directory of the example codes.