[omniORB] Configuring Naming Service -> I'm VERY Confused!!!
Gary D. Duzan
gdd0@gte.com
Tue, 13 Oct 1998 16:19:28 -0400
You're going to hate yourself for this one. You have to leave the "IOR:"
at the beginning of the string.
gdd0@lion { ~ } % catior -x IOR:012e65812800000049444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e746578743a312e3000010000000000000028000000010100000c0000003139322e3136382e302e3200393000000c000000352d399efff820f100000001
Type ID: "IDL:omg.org/CosNaming/NamingContext:1.0"
Profiles:
1. IIOP 1.0 192.168.0.2 12345 0x352d399efff820f100000001 (12 bytes)
gdd0@lion { ~ } %
Gary Duzan
GTE Laboratories
In Message <3625b008.25738238@smtp.ne.mediaone.net> ,
dmorgen@alum.mit.edu (David Morgenlender) wrote:
=>Sai-Lai,
=>
=>>> 3. How do I determine the correct IOR value for an already
=>>> initialized/started Naming Service? Is it taken from the cerr output
=>>> when it's next started? Is it taken from the log file? (None of =
=>these
=>>> values match the registry value on my Client!)
=>>
=>>Once omniNames has been run the first time, it will look at its log file=
=> to
=>>determine its root context (the initial object reference used by =
=>clients)
=>>in subsequent runs. It also prints the initial root context to cerr on
=>>startup.
=>>
=>>When you say the value does not match, you may just be seeing the =
=>padding
=>>bytes are different. Try catior -x <IOR string> to check out the IORs.
=>
=>I just tried catior & didn't get the results I was expecting:
=>
=>
=>Using the IOR from the client system's registry:
=>
=> catior -x 012e65812800000049444c3a6f6d672e6f72672f436f734e616d696e672
=> f4e616d696e67436f6e746578743a312e30000100000000000000280000000101
=> =
=>00000c0000003139322e3136382e302e3200393000000c000000352d399efff820f100000=
=>001
=>
=>I got the following results:
=>
=> Invalid stringified IOR supplied.
=> (Minor =3D 0)
=>
=>
=>Using the IOR from the server system's OMNIORB.CFG:
=> catior -x =
=>018c67812800000049444c3a6f6d672e6f72672f436f734e616d696e672f4e
=> 616d696e67436f6e746578743a312e3000010000000000000028000000010100000
=> =
=>c0000003139322e3136382e302e3200393000000c000000352d399efff820f100000001
=>
=>I got the same results as above.
=>
=>
=>
=>The catior commands were actually all on one line, in a batch file, =
=>executed
=>under Win95 on the client system.
=>
=>I tried both IORs with & without enclosing double quotes.
=>
=>I tried both with & without the Name Service & server running.
=>
=>The IORs used were taken from the locations where they were specified to =
=>be
=>taken from on the client & server systems.
=>
=>
=>Any suggestions?
=>
=>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=>=3D=3D=3D=3D=3D
=>Dave Morgenlender
=>e-mail: dmorgen@alum.mit.edu
=>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=>=3D=3D=3D=3D=3D
=>