下面是一个示例，用于测试在jvm由于不存在用户线程而退出时守护线程的行为。

请注意下面输出的倒数第二行，当主线程退出时，守护线程也死了，并且没有在finally块中打印finally executed9语句。这意味着如果由于不存在用户线程而导致JVM退出，守护线程finally块内关闭的任何i/o资源都不会被关闭。

public class DeamonTreadExample {

public static void main(String[] args) throws InterruptedException {

    Thread t = new Thread(() -> {
        int count = 0;
        while (true) {
            count++;
            try {
                System.out.println("inside try"+ count);
                Thread.currentThread().sleep(1000);
            } catch (InterruptedException e) {
                // TODO Auto-generated catch block
                e.printStackTrace();
            } finally {
                System.out.println("finally executed"+ count);
            }
        }
    });
    t.setDaemon(true);
    t.start();

    Thread.currentThread().sleep(10000);
    System.out.println("main thread exited");
  }
}

输出

inside try1
finally executed1
inside try2
finally executed2
inside try3
finally executed3
inside try4
finally executed4
inside try5
finally executed5
inside try6
finally executed6
inside try7
finally executed7
inside try8
finally executed8
inside try9
finally executed9
inside try10
main thread exited

Java有一种特殊的线程，称为守护线程。

非常低的优先级。 仅在同一程序没有其他线程正在运行时执行。 当守护线程结束时，JVM结束程序，完成这些线程 程序中运行的唯一线程。

守护线程用于什么?

通常用作普通线程的服务提供者。 通常有一个等待服务请求或执行线程任务的无限循环。 他们不能做重要的工作。(因为我们不知道它们什么时候会有CPU时间，如果没有任何其他线程在运行，它们可以在任何时间完成。)

这类线程的一个典型示例是Java垃圾收集器。

有更多的…

在调用start()方法之前，只能调用setDaemon()方法。线程运行后，就不能修改它的守护进程状态。 使用isDaemon()方法检查线程是守护线程还是用户线程。

我想澄清一个误解:

Assume that if daemon thread (say B) is created within user thread (say A); then ending of this user thread/parent thread (A) will not end the daemon thread/child thread (B) it has created; provided user thread is the only one currently running. So there is no parent-child relationship on thread ending. All daemon threads (irrespective of where it is created) will end once there is no single live user thread and that causes JVM to terminate. Even this is true for both (parent/child) are daemon threads. If a child thread created from a daemon thread then that is also a daemon thread. This won't need any explicit daemon thread flag setting. Similarly if a child thread created from a user thread then that is also a user thread, if you want to change it, then explicit daemon flag setting is needed before start of that child thread.

当最后一个非守护进程线程执行完成时，JVM将完成这项工作。默认情况下，JVM将创建一个线程作为非守护进程，但我们可以通过setDaemon(true)方法将线程创建为守护进程。Daemon线程的一个很好的例子是GC线程，它将在所有非Daemon线程完成后立即完成它的工作。

Daemon thread is like daemon process which is responsible for managing resources,a daemon thread is created by the Java VM to serve the user threads. example updating system for unix,unix is daemon process. child of daemon thread is always daemon thread,so by default daemon is false.you can check thread as daemon or user by using "isDaemon()" method. so daemon thread or daemon process are basically responsible for managing resources. for example when you starting jvm there is garbage collector running that is daemon thread whose priority is 1 that is lowest,which is managing memory. jvm is alive as long as user thread is alive,u can not kill daemon thread.jvm is responsible to kill daemon threads.

守护进程线程通常被称为“服务提供者”线程。这些线程不应该用来执行程序代码，而应该用来执行系统代码。这些线程与您的代码并行运行，但JVM可以随时终止它们。当JVM没有发现用户线程时，它将停止用户线程，所有守护进程线程立即终止。我们可以使用以下方法将非守护线程设置为守护线程:

setDaemon(true)