[omniORB] FW: Problem w/ Client/Server Communication Across L
AN With Client /Server NameServices
Smith, Wayne
wsmith2@titan.com
Wed Oct 16 20:00:01 2002
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C27546.1C345F30
Content-Type: text/plain;
charset="iso-8859-1"
catior on the IOR produced by :
genior IDL:omg.org/CosNaming/NamingContext:1.0 206.137.251.216 1234
NameService
yeilds:
Type ID: "IDL:omg.org/CosNaming/NamingContext:1.0"
Profiles:
1. IIOP 1.0 206.137.251.216 1234 "NameService"
catior on the IOR in omniNames.log yields:
Type ID: "IDL:omg.org/CosNaming/NamingContext:1.0"
Profiles:
1. IIOP 1.0 206.137.251.216 1234 "=.(...cB...."
The IOR with "=.(...cB...." is the one that works. The difference in the
IORs is the end of the string.
omniNames.log file contains the following snipet:
port 1234
create 3dac28f3ac86634200000002
bind
IOR:000000000000002849444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e6
7436f6e746578743a312e300000000001000000000000002c00010000000000103230362e313
3372
e3235312e3231360004d200000000000c3dac28f3ac86634200000002
EventChannelFactory
EventChannelFactory nobject
IOR:000000000000002e49444c3a4576656e744368616e6e656c41
646d696e2f4576656e744368616e6e656c466163746f72793a312e3000000000000001000000
0000
00002c00010000000000103230362e3133372e3235312e3231360004d300000000000c3dac28
f61e
fc135800000002
At the end of the first IOR in the "bind" before EventChannelFactory is the
same string as the string
following "create". I'm assuming this is the object ID as this is the only
difference in the IOR that produces
"NameService" in the Profiles portion of the output of catior with the
output of the above genior.
-----Original Message-----
From: bjorn rohde jensen [mailto:bjensen@fastmail.fm]
Sent: Wednesday, October 16, 2002 11:14 AM
To: Smith, Wayne
Cc: 'omniorb-list@omniorb-support.com'
Subject: Re: [omniORB] FW: Problem w/ Client/Server Communication Across
L AN With Client /Server NameServices
Hi Wayne,
The IOR published by omniNames given the parameters,
you listed, should only vary, if the ip-address of your
host changes. I have no idea, how object references
are actually encoded in IOR strings, but using omniORB's
catior tool on an omniNames IOR, i found, the most
derived interface of the object to be:
IDL:omg.org/CosNaming/NamingContextExt:1.0
That may explain the difference in the IORs, the objectId
should always be the string NameService.
Have you tried to turn up the tracelevels and seen, what
omniORB is unhappy about? You might also want to examine
the NameService IOR's with catior to verify their content.
Yours sincerely,
Bjorn
------_=_NextPart_001_01C27546.1C345F30
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [omniORB] FW: Problem w/ Client/Server Communication Across =
L AN With Client /Server NameServices</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>catior on the IOR produced by :</FONT>
</P>
<P> <FONT SIZE=3D2>genior =
IDL:omg.org/CosNaming/NamingContext:1.0 206.137.251.216 1234 =
NameService</FONT>
</P>
<P><FONT SIZE=3D2>yeilds:</FONT>
</P>
<P> <FONT SIZE=3D2>Type ID: =
"IDL:omg.org/CosNaming/NamingContext:1.0"</FONT>
<BR> <FONT =
SIZE=3D2>Profiles:</FONT>
<BR> <FONT SIZE=3D2>1. IIOP =
1.0 206.137.251.216 1234 "NameService"</FONT>
</P>
<P><FONT SIZE=3D2>catior on the IOR in omniNames.log yields:</FONT>
</P>
<P> <FONT SIZE=3D2>Type ID: =
"IDL:omg.org/CosNaming/NamingContext:1.0"</FONT>
<BR> <FONT =
SIZE=3D2>Profiles:</FONT>
<BR> <FONT SIZE=3D2>1. IIOP =
1.0 206.137.251.216 1234 "=3D.(...cB...."</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>The IOR with "=3D.(...cB...." is the one =
that works. The difference in the IORs is the end of the string.</FONT>
<BR><FONT SIZE=3D2>omniNames.log file contains the following =
snipet:</FONT>
</P>
<P> <FONT SIZE=3D2>port =
1234</FONT>
<BR> <FONT SIZE=3D2>create =
3dac28f3ac86634200000002</FONT>
<BR> <FONT SIZE=3D2>bind =
IOR:000000000000002849444c3a6f6d672e6f72672f436f734e616d696e672f4e616d69=
6e6</FONT>
<BR> <FONT =
SIZE=3D2>7436f6e746578743a312e300000000001000000000000002c00010000000000=
103230362e3133372</FONT>
<BR> <FONT =
SIZE=3D2>e3235312e3231360004d200000000000c3dac28f3ac86634200000002 =
EventChannelFactory </FONT>
<BR> <FONT =
SIZE=3D2>EventChannelFactory nobject =
IOR:000000000000002e49444c3a4576656e744368616e6e656c41</FONT>
<BR> <FONT =
SIZE=3D2>646d696e2f4576656e744368616e6e656c466163746f72793a312e300000000=
00000010000000000</FONT>
<BR> <FONT =
SIZE=3D2>00002c00010000000000103230362e3133372e3235312e3231360004d300000=
000000c3dac28f61e</FONT>
<BR> <FONT =
SIZE=3D2>fc135800000002 &=
nbsp; </FONT>
</P>
<P><FONT SIZE=3D2>At the end of the first IOR in the "bind" =
before EventChannelFactory is the same string as the string </FONT>
<BR><FONT SIZE=3D2>following "create". I'm assuming this is =
the object ID as this is the only difference in the IOR that =
produces</FONT>
<BR><FONT SIZE=3D2>"NameService" in the Profiles portion of =
the output of catior with the output of the above genior. </FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: bjorn rohde jensen [<A =
HREF=3D"mailto:bjensen@fastmail.fm">mailto:bjensen@fastmail.fm</A>]</FON=
T>
<BR><FONT SIZE=3D2>Sent: Wednesday, October 16, 2002 11:14 AM</FONT>
<BR><FONT SIZE=3D2>To: Smith, Wayne</FONT>
<BR><FONT SIZE=3D2>Cc: 'omniorb-list@omniorb-support.com'</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [omniORB] FW: Problem w/ Client/Server =
Communication Across</FONT>
<BR><FONT SIZE=3D2>L AN With Client /Server NameServices</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Hi Wayne,</FONT>
</P>
<P><FONT SIZE=3D2> The IOR published by omniNames given the =
parameters,</FONT>
<BR><FONT SIZE=3D2>you listed, should only vary, if the ip-address of =
your</FONT>
<BR><FONT SIZE=3D2>host changes. I have no idea, how object =
references</FONT>
<BR><FONT SIZE=3D2>are actually encoded in IOR strings, but using =
omniORB's</FONT>
<BR><FONT SIZE=3D2>catior tool on an omniNames IOR, i found, the =
most</FONT>
<BR><FONT SIZE=3D2>derived interface of the object to be:</FONT>
</P>
<P><FONT SIZE=3D2>IDL:omg.org/CosNaming/NamingContextExt:1.0</FONT>
</P>
<P><FONT SIZE=3D2>That may explain the difference in the IORs, the =
objectId</FONT>
<BR><FONT SIZE=3D2>should always be the string NameService.</FONT>
<BR><FONT SIZE=3D2> Have you tried to turn up the tracelevels and =
seen, what</FONT>
<BR><FONT SIZE=3D2>omniORB is unhappy about? You might also want to =
examine</FONT>
<BR><FONT SIZE=3D2>the NameService IOR's with catior to verify their =
content.</FONT>
</P>
<P><FONT SIZE=3D2>Yours sincerely,</FONT>
</P>
<P><FONT SIZE=3D2>Bjorn</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C27546.1C345F30--