[omniORB] outScavenger kill
Renzo Tomaselli
renzo.tomaselli@eclipse-net.it
Fri, 22 Jan 1999 10:16:36 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_01AD_01BE45F0.4B0021C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
we experienced a problem with Visual Basic managing an OCX which =
links to an OmniORB related implementation. When switching from design =
mode to run mode and the contrary, Visual Basic crashes because DLLs are =
unloaded from memory, while the outScavenger thread is still alive. When =
the timer wakes it up, there is no loaded code to run and everything =
blows up.
We cannot understand how VB unloads depending modules while active =
threads are still alive (it doesn't happen with VC).
Anyway, the problem is that killOutScavenger is never called from =
OmniORB code; also there is no explicit ORB shutdown to call when all =
things are going to die.
>From the BOA point of view there are impl_is_ready/impl_shutdown entry =
points which do the correct job for inScavenger, so everythings works =
fine there.
What about explicitely calling killOutScavenger from a key application =
destructor when things go down ?
Thanks,
Renzo =
Tomaselli =20
-------------------------------------------------------------------------=
--
TecnoTP s.n.c. Special Information System Design
Maso Pelauchi I38050 Ronchi Valsugana, Trento TN ITALY
Tel. +39 0461 773164 Fax. +39 0461 771514
e-mail: renzo.tomaselli@eclipse-net.it =20
-------------------------------------------------------------------------=
--
------=_NextPart_000_01AD_01BE45F0.4B0021C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3007.2"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>Hi,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2> we experienced a =
problem with=20
Visual Basic managing an OCX which links to an OmniORB related =
implementation.=20
When switching from design mode to run mode and the contrary, Visual =
Basic=20
crashes because DLLs are unloaded from memory, while the outScavenger =
thread is=20
still alive. When the timer wakes it up, there is no loaded code to run =
and=20
everything blows up.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT><FONT size=3D2>We cannot =
understand how VB=20
unloads depending modules while active threads are still alive (it =
doesn't=20
happen with VC).</FONT></DIV>
<DIV><FONT size=3D2>Anyway, the problem is that killOutScavenger is =
never called=20
from OmniORB code; also there is no explicit ORB shutdown to call when =
all=20
things are going to die.</FONT></DIV>
<DIV><FONT size=3D2>From the BOA point of view there are=20
impl_is_ready/impl_shutdown entry points which do the correct job for=20
inScavenger, so everythings works fine there.</FONT></DIV>
<DIV><FONT size=3D2>What about explicitely calling killOutScavenger from =
a key=20
application destructor when things go down ?</FONT></DIV>
<DIV><FONT size=3D2>Thanks,</FONT></DIV>
<DIV><FONT color=3D#000000=20
size=3D2> &nbs=
p;  =
; =
&=
nbsp; &n=
bsp; =20
Renzo Tomaselli =20
<BR>---------------------------------------------------------------------=
------<BR>TecnoTP=20
s.n.c. Special Information System Design<BR>Maso Pelauchi I38050 Ronchi=20
Valsugana, Trento TN ITALY<BR>Tel. +39 0461=20
773164 Fax. +39 0461 771514<BR>e-mail: <A=20
href=3D"mailto:renzo.tomaselli@eclipse-net.it">renzo.tomaselli@eclipse-ne=
t.it</A> =20
<BR>---------------------------------------------------------------------=
------</FONT></DIV></BODY></HTML>
------=_NextPart_000_01AD_01BE45F0.4B0021C0--