[omniORB] omniORB4: LONG Pause during orb->shutdown(0), orb->destroy()

[Duncan Grisby]

On Friday 30 November, Ken Feuerman wrote:

> Good news (well, from my point of view anyway):  I can indeed reproduce 
> this problem using the call_back example.  Here's what the console output 
> looks like on the cb_client side.  I've added two annotations to indicate 
> where the long pauses occur:

That will teach me not to test it on Windows. The problem was a
re-occurrence of something that was fixed in omniORB 3. Windows
doesn't report socket errors on select() after the socket has been
shutdown, so we have to keep a note of it elsewhere.

It's fixed now in CVS. Sometimes you'll find that it takes a second or
two to shut down, while it waits for the select to time out. I'm
afraid that that's just a consequence of Windows' strange socket
model.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --