I don't know if this helps but you can always call inerrupt() on the thread.
This causes the thread to throw an InterruptedException. Which will cause
most code to exit unless they catch Exception in the main loop and restart.
-dain
----- Original Message -----
From: "Peter Fagerlund" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 25, 2001 6:32 AM
Subject: Re: [JBoss-dev] zombie thread-> bug
> on 1-06-25 08.27, marc fleury at [EMAIL PROTECTED] wrote:
> > it seems two processes, webserver (dynaserver) and hypersonicSQL do not
> > close properly on Linux and don't really close their threads like it
they
> > are supposed to.
>
> Do the "shutdownhook" get installed ? (on Linux (VM ?)) - and jmx is
calling
> stopService() in the hsql MBean ???
>
> > That is usually due to the fact that thread.destroy is not implemented
and
> > it is recommended to set a flag in your code to properly shut down the
> > thread.
>
> I do not understand ! ? well the serverSocket is started - maybe add them
> into a threadGroup that gets teared down ??? since the other threads seem
to
> get cleared alltho i suspect the shutdownhook is not installed ...
>
> ahhh - kill pid and have a threadGroup for the SS'ets ! ?
>
> > in any case it is a bug in both dynaserver and hypersonic :(
>
> oki if the MBean.stopServer gets called then its a bug in those services
> otherwise it has to do with the linux vm and the way the shutdownhook is
> implemented ... do i recall a earlier post on this ??? ... I do not know
> since I do nothave a unified search - but have now serched in 3 places on
> the web user/dev/manual ... and some are there ...
>
> /peter
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
