[omniORB] Tracing options - Rel. 3.0.2

[Ivanov, Roumen]

Thanks, Duncan,
I've been considering that (regarding the bug), but for some reasons I
couldn't use CVS to apply only the bug fixes to some release and I didn't
want to use a daily snapshot which might possibly introduce some other bugs.
What about 3.0.5 or exposing a downloadable version of 3.0.4 with applied
known bugs fixes?

Although an experiment worths. Let me ask - is it supposed clients, compiled
with 3.0.2, to work using the DLLs for 3.0.4. Is this what you are calling
binary compatibility and, if so, for what versioning level is works?

Regards,
Roumen


-----Original Message-----
From:	Duncan Grisby [SMTP:dgrisby@uk.research.att.com]
Sent:	Tuesday, January 29, 2002 12:01
To:	Ivanov, Roumen
Cc:	'omniorb list'
Subject:	Re: [omniORB] Tracing options - Rel. 3.0.2 

On Tuesday 22 January, "Ivanov, Roumen" wrote:

> 	When the number of clients reaches a particular number (about 123)
> no more clients could connect.

There was a bug in omniORB 3.0.4 and before that meant that it would
sometimes deadlock if thread creation failed. Can you try updating to
the latest CVS snapshot and see if that helps?

Another possibility is for you to try the omniORB 4 pre-release. That
supports a thread pool model, which might be helpful with large
numbers of clients.

Cheers,

Duncan.

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