[omniORB] Strange IOR

[Frederic Prin]

Hi all,

I have some IOR registered on my Name Service that are dangling (the
corresponding server is dead).
When a clients tries to resolve + _narrow it I catch a TRANSIENT
exception when trying to narrow (that is good) but with a bad minor code
= 0x41540008
Which is omni::TRANSIENT_CallTimedout !

Indeed, I do set a setClientCallTimeout() before the narrow call but
since the IOR points on a dead server the servant cannot be contacted so
I am expecting another minor code.

I tried to get more information on those IOR with catior but
unfortunatly it fails with a MARSHALL exception


	meije{ bin }:14 > catior
IOR:010000001f00000049444c3a49536d617274566965772f5356496e74657266616365
3a312e300000010000000000000060000000010102000c00000031302e36362e31302e31
3300008100000e000000fec79cf2400000544d0000000000000002000000000000000100
000001000000010000001c00000001000000010001000100000001000105090101000100
000009010100
	Type ID: "IDL:ISmartView/SVInterface:1.0"
	Profiles:
	1. IIOP 1.2 10.66.10.13 33024 ".... at ..TM....."

	Invalid stringified IOR supplied.
	(CORBA::MARSHAL: minor = MARSHAL_PassEndOfMessage)

(I copy/paste the IOR from a kind of Name Service explorer (not of my
own) maybe it is wrongly displayed)

Any ideas

Thanks

Fred
                              (
     Frédéric Prin          )
     Senior Software Engineer /
          S I L V A C O      (
     Grenoble REsearch CEnter \
     Tel 04 56 38 10 33        )
    __________________________/___
   /__/__/__/__/__/__/__/__/__/__/
  /__/__/__/__/__/__/__/__/_____/
 /__/__/__/__/__/__/__/__/__/__/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20040729/88e443c5/attachment.htm