[omniORB] timeout on location forwarded object reference

[Lee, Robert C.]

Yes, it does repeatedly throw giopStream, reverting, invocation etc, etc.

I solved this problem by installing an handler:

omniORB::installTransientExceptionHandler (0, my_transient_handler);

CORBA::Boolean my_transient_handler(void* cookie,
        CORBA::ULong retries,
        const CORBA::TRANSIENT& ex)
{
   if (retries >= 3)
        return false;
   else
        return true;
}

Now, after 3 tries, I get an exception thrown that I can catch and handle.
Perhaps my trying to use the timeout features didn't work, so I did this
instead.

Is my approach the correct one or was I just lucky?

Thanks,
Robert

-----Original Message-----
From: Duncan Grisby [mailto:duncan at grisby.org]
Sent: Wednesday, February 11, 2004 8:43 AM
To: Lee, Robert C.
Cc: 'omniORB-list at omniorb-support.com'
Subject: Re: [omniORB] timeout on location forwarded object reference 


On Friday 23 January, "Lee, Robert C." wrote:

> Why does a server time out when it fails to complete a call on an object
due
> to this problem:
> 
> omniORB: throw giopStream::CommFailure from
> giopStream.cc:1070(0,NO,TRANSIENT_ConnectFailed)
> omniORB: Reverting object reference to original profile
> omniORB: Invocation on a location forwarded object has failed. 86 retries
> 
> Shouldn't it try to make the call on the original profile and then quit?
I
> have the clientCallTimeOutPeriod = 5000 so shouldn't have just quit after
5
> seconds?

I don't quite understand the question. Are you saying that the client
keeps reverting to the original profile, and the original location
keeps forwarding it to a broken location?  If so, I'd say that omniORB
should not time out since it's not waiting for a response -- it's
repeatedly getting a broken response.

Can you clarify exactly what the situation is?

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --