🚀 go-pugleaf

On Mon, 29 Nov 1999 12:12:10 +0100, tluyben wrote:

> > Calling System.exit() will stop the program.
> 
> Which will also result in terminating my servletrunner (jws for instance).
> So this is not a good solution...

You could also hunt down the threads and do a thread.stop() on them.

I am curious -- Why are you using a Toolkit from a servlet?

-- 
John P. McGrath
<JPMcGrath@fast.net>
<jpm@nscs.fast.net>


> "John P. McGrath" wrote:
> 
> > On Wed, 24 Nov 1999 23:12:32 +0100, tluyben wrote:
> >
> > > The following piece of code NEVER ends...
> > > I'm running this from a servlet and because 3 AWT
> > > threads in the VM never end, my memory gets sucked
> > > up.
> >
> > > import java.awt.*;
> > > public class ThreadsAreStuck {
> > >     public static void main(String args[]) {
> > >         Toolkit.getDefaultToolkit();
> > >     }
> > > }
> >
> > I think what is happening is that Toolkit.getDefaultToolkit() initializes
> > the AWT, which causes several non-daemon threads to be created.  Since
> > the threads are still active, the program does not end when the program
> > drops off the end of the main() method.
> >
> > This is exactly the same situation you will see if you display a frame
> > and then later close it.  The AWT threads are still running, so the
> > program continues.
> >
> > Calling System.exit() will stop the program.
> >
> 
> Which will also result in terminating my servletrunner (jws for instance).
> So this is not a good solution...
> 
> Thanks anyway!
> 
> >
> > --
> > John P. McGrath
> > <JPMcGrath@fast.net>
> > <jpm@nscs.fast.net>
> 
>