Bug 428 - IOR generated by Event_Service on win98 contains an invalid tag
Summary: IOR generated by Event_Service on win98 contains an invalid tag
Status: RESOLVED
Alias: None
Product: TAO
Classification: Unclassified
Component: orbsvcs (show other bugs)
Version: 1.0.9
Hardware: x86 Windows 98
: P2 normal
Assignee: DOC Center Support List (internal)
URL:
Depends on:
Blocks:
 
Reported: 2000-02-16 05:30 CST by Sandro Doro
Modified: 2000-02-17 23:27 CST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sandro Doro 2000-02-16 05:30:42 CST
Hi,

  I am running a standard Name_Service in {NT, Linux} box and run Event_Service
on a win98 box. When I look at IOR, the Event_Service (and Schedule_Service)
contain a more long profile. Looking with NamingViewer utility I see two
reference:
1. IOP1.1@HOST:PORT
2. unknow 54414F02       <-----

Also using catior (in a Linux box) the result is same:

reading the file /tmp/a4

here is the IOR
IOR:010000002000000049444c3a527465635363686564756c65722f5363686564756c65723a312e3000020000000000000070000000010101000a0000005345435245544152590035041b00000014010f00525354f181aa38a0f703000000000001000000010000000003000000000000000800000001cdcdcd004f4154010000001400000001cdcdcd01000100000000000901010000000000004f41540400000001cd0000024f415470000000010101cd0a0000005345435245544152590036041b00000014010f00525354f181aa38a0f70300000000000100000001000000cd03000000000000000800000001cdcdcd004f4154010000001400000001cdcdcd01000100000000000901010000000000004f41540400000001cd0000
decoding an IOR:
The Byte Order: Little Endian
The Type Id:    "IDL:RtecScheduler/Scheduler:1.0"
Profile Count:  1
IIOP Version:   1.1
  Host Name:    SECRETARY
  Port Number:  1077
  Object Key len:   27
  Object Key as hex:
  14 01 0f 00 52 53 54 f1 81 aa 38 a0 f7 03 00 00
  00 00 00 01 00 00 00 01 00 00 00
  The Object Key as string:
  ....RST...8................
  The component <0> has tag <0>
    Component Value len:    8
    Component Value as hex:
    01 cd cd cd 00 4f 41 54
    The Component Value as string:
    .....OAT
  The component <1> has tag <1>
    Component Value len:    20
    Component Value as hex:
    01 cd cd cd 01 00 01 00 00 00 00 00 09 01 01 00
    00 00 00 00
    The Component Value as string:
    ....................
  The component <2> has tag <1413566208>
    Component Value len:    4
    Component Value as hex:
    01 cd 00 00
    The Component Value as string:
    ....
Profile Count:  2
  unknown tag 1413566210 skipping    <------ in hex is 54414F02
catior returned true


Note: If I try to start Event_Service with -ORBEndpoint iiop://1.1@HOST:PORT the
IOR is correct.
Comment 1 Carlos O'Ryan 2000-02-17 23:27:59 CST
This is not a bug the IOR is the new shared memory protocol. I have updated
catior to print the correct protocol when it finds a SHMIOP profile.
I'm not sure if Win98 supports shared memory or not, but it should not be a
problem in any case.