From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,97d2772750ae15ad
X-Google-Attributes: gid103376,public
X-Google-Thread: f753e,97d2772750ae15ad
X-Google-Attributes: gidf753e,public
From: SpamSpamSpam <spam@spam.com>
Subject: Re: Extended comm loss and TCP/IP
Date: 1999/04/15
Message-ID: <3715E442.C4FD1402@spam.com>#1/1
X-Deja-AN: 466709318
Content-Transfer-Encoding: 7bit
References: <37142321.E3B0C8BE@pacbell.net> <3715C3E5.46C5704B@spam.com>
Content-Type: text/plain; charset=us-ascii
Organization: spameater
Mime-Version: 1.0
Newsgroups: comp.lang.ada,comp.object.corba
Date: 1999-04-15T00:00:00+00:00
List-Id: <comp.lang.ada>

.. to escape the declare block on comms failure, you also have to call "abort CorbaCall"after
the timeout delay.  If the actual Corba Call is a rendezvous with the ORBExpress
implementation, then it will still be held, the task can't terminate and you can't leave the
declare block............

>        Delay ( RoughTimeout ) ;

>        abort CorbaCall ;