Re: Problem with ORBit2 Client connecting to Jacorb Name Server

[Frank Rehberger <Frank Rehberger web de>]

just two cents:

AFAICS, in Jacorb reply-message the endianess does not suffice CORBA spec,

ORBit2 is sending request-id  as little-endianness "10 e4 ff bf " and 
Jacorb uses big-endiannes in reply message "bf ff e4 10".  To be CORBA 
compliant,  server should use same endiannes in reply the client is 
using, isn't it? It seems, Jacorb does not care about endiannes in 
request-message.

But, AFAICS, in this case ORBit2 process should never reach the point 
where SEGV occures :/


> Marshal: id 0xbfffe410
> 'n' : kind - 18, i 'UserManager')Outgoing IIOP data:
> 0x0000:   47 49 4f 50  01 02 01 00  6c 00 00 00  XX XX XX XX | 
> GIOP....l...****
> ---
> 0x000c:   10 e4 ff bf  03 00 00 00  00 00 00 00  1f 00 00 00 | 
> ................ 

^^^^^^^^^^^^^^^^^^^^^

> ---
> Incoming IIOP header:
> 0x0000:   47 49 4f 50  01 02 00 01  00 00 00 ec  XX XX XX XX | 
> GIOP........****
> ---
> Incoming IIOP body:
> 0x000c:   bf ff e4 10  00 00 00 00  00 00 00 00  00 00 00 29 | 
> ...............)

^^^^^^^^^^^^^^^^^^^^

Regards, Frank