File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Threads and Synchronization and the fly likes Do all running threads stop when JVM exits? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Java » Threads and Synchronization
Bookmark "Do all running threads stop when JVM exits?" Watch "Do all running threads stop when JVM exits?" New topic
Author

Do all running threads stop when JVM exits?

Rue Fi
Greenhorn

Joined: Jul 08, 2006
Posts: 7
Do all running threads stop when you issue a command such as System.exit(0) and exit the JVM?
Henry Wong
author
Sheriff

Joined: Sep 28, 2004
Posts: 18896
    
  40

When the JVM exits, *all* threads running in the JVM will terminate.

Henry


Books: Java Threads, 3rd Edition, Jini in a Nutshell, and Java Gems (contributor)
Peter Chase
Ranch Hand

Joined: Oct 30, 2001
Posts: 1970
Yes, if you System.exit(), then all threads (even native ones) will stop, because System.exit() blows away the process (in the JVMs that I know, anyway).

However, your Java program generally should not System.exit() unless it really has to. When you System.exit(), all threads stop, regardless of what they were doing at the time. Also, using System.exit() makes your code unsuitable for re-use in a Web applictation or other application server, because System.exit() will kill the whole process, not just the particular bit of the process that's running your particular application.

Instead of using System.exit(), you should arrange for all your non-daemon threads to exit cleanly. Perhaps you can use Thread.interrupt(). Perhaps you can have some sort of global shut-down flag that all threads check every now and then. Perhaps some of your threads should be daemons, so they do not delay JVM shut-down.

If your application uses graphics (Swing/AWT), then there is an extra issue. You need to make sure that none of your windows has the default parent. Instead, you should create your own dummy Frame as a parent for all of them. When it's time to shut down, you should dispose() that Frame. Then the application can shut down cleanly, without System.exit().


Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.
Mingwei Jiang
Ranch Hand

Joined: Feb 19, 2004
Posts: 63
So, if it is the System.exit. Will it interrupt all running threads by calling thread.interrupt()?
Peter Chase
Ranch Hand

Joined: Oct 30, 2001
Posts: 1970
No, System.exit() just kills the whole process, which can be bad in any but the simplest application. That's why you should design your program to exit cleanly, without the use of System.exit().
Douglas Chorpita
Ranch Hand

Joined: May 09, 2006
Posts: 97
How a JVM implements its threads internally is an implementation detail and can vary from one JVM to another. When the JVM shuts down, it doesn't have to call any Java code, as the JVM itself is the thread manager (or simulator). Java Thread objects are mere abstractions of JVM threads.

...and JVM threads are generally abstractions of operating system threads, which are in turn abstractions of physical microprocessor threads.


SCJP 1.4 - 95%
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Do all running threads stop when JVM exits?