[omniORB] a probably stupid multithread question

[Duncan Grisby]

On Friday 9 November, Matthias Hilmer wrote:

> i have the following problem: when i start my client multithreded with 10
> threads each open working on the server and echo the server object's
> thread id back to the client i get 5 different id's instead of the
> expected 10 although the client threads are still alive. Doesn't omniORB
> work multithreaded? I do know from TAO, that there is a 3. param to
> ORB._init() which is needed to identify the clientside thread correctly.
> But omniORB doesn't have that param. I found
> omniORB::maxTcpConnectionPerServer in the manual. But setting this to 100
> doesn't seem to have an efect.

What you are seeing is indeed due to the maxTcpConnectionPerServer
setting. Changing it should have made a difference. Make sure you are
specifying the setting on the client, not the server.

Cheers,

Duncan.

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