[omniORB] omniORB threads dieing

Mon, 11 Feb 2002 20:30:08 -0500

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1B364.CEB11DA0
Content-Type: text/plain;
	charset="iso-8859-1"

I am using omniORB 3.0.3 on IRIX
I understand that omniORB does some housekeeping in order not to eat up all
the machine's resources after a while. Amongst other things it seems to
terminate threads that have not been used for a while. (correct?)

This is a problem for me. My server application has a problem when the
(omni-) thread that made a call terminates. My code will delete a couple of
other resources that are coupled to the lifetime of the thread that first
created them. Although it would certainly be possible to change this (so
that these resources are not coupled to the lifetime of the creating thread
anymore) ... this would break my design quite a bit. 

I do know that there will never be more than two calls made to this server
application at the same time. So I do not have to worry about more and more
threads getting created by omniORB. I wonder if there is a way to witch of
this automatic housekeeping.

I tried  -ORBscanGranularity 0

--
H. Henning Schmidt / Thomson Multimedia
http://www.thomsonbroadcast.com
SchmidtH@THmulti.com

------_=_NextPart_001_01C1B364.CEB11DA0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>omniORB threads dieing</TITLE>
</HEAD>
<BODY>

I am using omniORB 3.0.3 on =
IRIX
 I understand that omniORB does some =
housekeeping in order not to eat up all the machine's resources after a =
while. Amongst other things it seems to terminate threads that have not =
been used for a while. (correct?)

This is a problem for me. My server =
application has a problem when the (omni-) thread that made a call =
terminates. My code will delete a couple of other resources that are =
coupled to the lifetime of the thread that first created them. Although =
it would certainly be possible to change this (so that these resources =
are not coupled to the lifetime of the creating thread anymore) ... =
this would break my design quite a bit.

I do know that there will never be =
more than two calls made to this server application at the same time. =
So I do not have to worry about more and more threads getting created =
by omniORB. I wonder if there is a way to witch of this automatic =
housekeeping.

<P><FONT SIZE=3D2 FACE=3D"Arial">I tried&nbsp; -ORBscanGranularity =
0</FONT>
</P>
<BR>

--
 H. Henning Schmidt / Thomson =
Multimedia
 <A =
HREF=3D"http://www.thomsonbroadcast.com" =
TARGET=3D"_blank">http://www.thomsonbroadcast.com</A>
 SchmidtH@THmulti.com

</BODY>
</HTML>
------_=_NextPart_001_01C1B364.CEB11DA0--