Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <00dd01c5e34c$68df2000$0a0f1aac@IBM1048BF2B560>
From: "Augmentin" <augmentin@hkbn.net>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Subject: how to stop user app daemon threads in tomcat webapps?
Date: Mon, 7 Nov 2005 11:36:16 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00DA_01C5E38F.76ED0340"

------=_NextPart_000_00DA_01C5E38F.76ED0340
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: quoted-printable

Hi,

I found that the daemon threads created by my Tomcat webapp won't =
automatically stop when the webapp itself is stopped or =
undeployed/redeployed.

As Tomcat itself is a java application there will always be user threads =
in the jvm even when your webapp is stopped.. which makes the daemon =
threads spawned by webapps never stop.

I tried to add a finalize() method to a main object in the webapp to =
interrupt the daemon threads but it didn't seem to work... the timing of =
call to finalize() is undetermined, only when it performs garbage =
collection. And many times it seemed that when my webapp is =
stopped/reloaded/undeployed/redeployed the objects were just not =
properly finalized or garbage collected at all.

I am using Tomcat 5.5.9 on Windows XP Pro and Solaris 2.6.

Thank you for your help.
Raymond.
------=_NextPart_000_00DA_01C5E38F.76ED0340--