[omniORB] The thread-specific data destroyed in tread-pool policy thread model.

[Duncan Grisby]

On Monday 27 March, "Michal Misiaszek" wrote:

> I have following problem. In our server we are using thread specific data
> structure to keep some information. 
> We are using thread-pool policy model in server and we are having many
> clients connected to it. Recently we have strange problem with application
> which was identified as destruction of thread specific data between client
> calls. I beloved that in case of thread-pool threads are not destroyed but
> only created when necessary (as pool is not initialized). Did I get
> something wrong ?

Yes, you misunderstood. See section 8.4.2 of the omniORB manual:

  "The thread pool is not pre-initialised. Instead, threads are started
   on demand, and idle threads are stopped after a period of inactivity"

The default timeout for idle threads is 10 seconds. If you really need
to prevent threads being stopped, you can set
omniAsyncInvoker::idle_timeout to a much larger number of seconds.

Cheers,

Duncan.

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