[omniORB] why multiple async workers for one connection

[Duncan Grisby]

On Friday 14 November, "Renzo Tomaselli" wrote:

>     within the search for a solution to our AIX problem - which I described
> in a previous posting - I wonder if anybody can explain me why a simple
> client, a python script performing a tight loop on the same obj ref. method,
> ends up with multiple worker threads in the server.

No, I can't explain that. I would not expect a second worker to be
created for a single threaded client in thread per connection mode.
What happens in the log just before the new worker thread starts?
Please try running with traceThreadId set true. That will make it
easier to understand the logs.

Cheers,

Duncan.

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