Problem setting DefaultQoS with Notification Service

Niclas Eklund nick@REDACTED
Thu May 3 12:54:47 CEST 2001


On Wed, 2 May 2001, Jani Launonen wrote:
> [cut plenty]
> Orber version is 3.2.2. Frankly, I don't know for sure, that the wstrings
> are to blame, but Mr. Björn Wingman have encountered the same problem (
> http://lists.spline.inf.fu-berlin.de/mailman/htdig/jacorb-developer/2001-February/001539.html
> ). Before I applied the fix for JacORB 1.3.21 fix for TypeCode (
> http://jacorb.inf.fu-berlin.de/problemscontents.html ) the symptoms were
> the same as Björn had. After the patch, dior (dump ior) reports little bit
> different problem. Here's what the dior has to say about channel's ior:

I assume the result is a INV_OBJREF exception?!
The Code Set Id have been changed (Orber-3.2.3). Update to:

orber_iiop.hrl: -define(ISO_10646_UCS_2_ID, 16#00010100).

Now it should work.

Regards / Nick


>         JacORB V 1.3.21, www.jacorb.org
>         (C) Gerald Brose, FU Berlin, 28 March 2001
> ------IOR components-----
> TypeId  :       IDL:omg.org/CosNotifyChannelAdmin/EventChannel:1.0
> TAG_INTERNET_IOP Profiles:
>         Profile Id   :          IIOP Version :  1.1
>         Host    :       130.231.48.51
>         Port    :       4001
>         Object key (hex):    0x4F 52 42 45 52 83 68 06 6D 00 00 00 32 49 44
> 4C 3A 6F 6D 67 2E 6F 72 67 2F 43 6F 73 4E 6F 74 69 66 79 43 68 61 6E 6E 65
> 6C 41 64 6D 69 6E 2F 45 76 65 6E 74 43 68 61 6E 6E 65 6C 3A 31 2E 30 64 00
> 03 6B 65 79 6D 00 00 00 25 83 68 02 68 03 62 00 00 03 DC 62 00 0C A2 89 62
> 00 01 02 BA 64 00 0E 61 40 74 6B 31 31 2E 6F 75 6C 75 2E 66 69 6D 00 00 00
> 0D 83 64 00 09 75 6E 64 65 66 69 6E 65 64 6D 00 00 00 0D 83 64 00 09 75 6E
> 64 65 66 69 6E 65 64 6D 00 00 00 0D 83 64 00 09 75 6E 64 65 66 69 6E 65 64
> TAG_MULTIPLE_COMPONENTS Profiles:
>         CodeSet Component Info:
>                 ForChar native code set Id: ISO8859_1
>                 Char Conversion Code Sets:              ForWChar native
> code set Id: Unknown TCS: 3e8
>                 WChar Conversion Code Sets:
> 
> So it seems that something is still wrong with the wstrings? I haven't had
> chance to try decode this ior with anything else besides JacORB's dior.
> Could there still be problem with JacORB or is the ior corrupted by Orber?
> Here's the ior just for sure, if you want to try it for yourself:


_____________________________________________________________
Niclas Eklund, Ericsson Network Core Products, +46-8-72 75765





More information about the erlang-questions mailing list