[omniORB] Client hangs for some time between LocateRequest calls

[Serguei Kolos]

Duncan Grisby wrote:

>On Wednesday 1 October, Serguei Kolos wrote:
>
>  
>
>>Below is the part of the output produced by the listing application with 
>>traceLevel=50.
>>Does anybody have a clue to this issue?
>>    
>>
>
>[...]
>  
>
>>omniORB: LocateRequest to remote: 
>>root/POA[ipc/test][ipc_test_object_0]<ipc.test.object.170>
>>
>>
>>///////////// 2 - 3 seconds delay: nothing is happening
>>
>>
>>omniORB: throw giopStream::CommFailure from 
>>giopStream.cc:1061(0,NO,TRANSIENT_ConnectFailed)
>>    
>>
>
>I suspect that it's just that whatever machine it's trying to connect
>to is taking a few seconds to respond with a connection failure.
>Coincidentally, I checked in a change a while ago that prints out the
>address it's trying to connect to, so if you update from CVS, you'll
>see extra logging telling you which server it's trying to connect to
>when it takes a long time. Alternatively, print out the stringified
>IOR of each object reference before you try to call it, and decode the
>output with catior.
>
I am sure this is not the case, because all the objects were incarnated 
in the same process, so
the client must always try to connect to the same machine.

>If that isn't the issue, I can only guess that it's the OS taking time
>to clear up the remains of all the failed connections.
>
This sounds like a probable reason. May be somebody knows how to tune up 
the OS to avoid such
situations.

Cheers,
Sergei
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20031006/379f2c42/attachment-0001.htm