[omniORB] problem using ThreadPool in OmniORB

[Duncan Grisby]

On Thursday 22 May, Malge Nishant wrote:

> 	If I restart my server and if client issues directly GIOP::Request
> then the Server throws an OBJECT_NOT_EXIST and returns without setting the
> connection to be watch-able so when worker thread calls notifyWkDone, the
> Peek call returns false. This is true only in case of ThreadPool because in
> ThreadPerConnection a thread is dedicated to serve the connection till it is
> open.

Ah yes. Thanks for tracking that down. I have checked in a fix.

Cheers,

Duncan.

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