[omniORB] COMM_FAILURE when invoking _nonexistent() on object

[Sai-Lai Lo]

In omniORB 3 or earlier, failure to communicate with the server has always
been reported as COMM_FAILURE. The latest spec, (I believe starting from
CORBA 2.3 or so), stated that this situation should be reported as
TRANSIENT.  The ORB implementation has not caught up with this change.

By the way, omniORB 4 does use TRANSIENT to report this kind of failure.

Sai-Lai



----- Original Message -----
From: "Stephen Crawley" <crawley@dstc.edu.au>
To: "Kirkpatrick, James E" <james.e.kirkpatrick@lmco.com>
Cc: <omniorb-list@uk.research.att.com>; <crawley@dstc.edu.au>
Sent: Thursday, June 28, 2001 3:15 AM
Subject: Re: [omniORB] COMM_FAILURE when invoking _nonexistent() on object


>
> James,
>
> You should be seeing TRANSIENT if you call '_non_existent()' or a
> user-defined 'ping()' operation while the server is down.
>
> In this case, you should not see COMM_FAILURE.  That exception is
> supposed to mean that the server has died in the middle of an operation.
>
> You should not get OBJECT_NOT_EXIST if the server is simply not running.
> This exception is supposed to mean the the object has gone away for
> ever.  If the server is not inaccessible, there is not way (in OmniORB)
> to make that determination.
>
> If OmniORB is doing something different, it is not compliant, IMO.
>
> -- Steve
>
>
>
>