JDK 定时任务 Timer 与 ScheduledExecutorService 排坑记录

代码星冰乐

专注成就未来

首页 归档 关于

JDK 定时任务 Timer 与 ScheduledExecutorService 排坑记录

Jul 18, 2018 | haifeiWu | Java | 阅读
文章目录
  1. 1. 定时任务，关于 Timer 与 ScheduledExecutorService 的抉择
    1. 1.1. Timer 存在的问题
    2. 1.2. 使用 ScheduledExecutorService
  2. 2. 产生的问题
    1. 2.1. 查日志
    2. 2.2. 扒源码
  3. 3. 复盘
  4. 4. 问题解决
  5. 5. 小结

作 者：haifeiWu
原文链接：https://www.hchstudio.cn/article/2018/b903/
版权声明：非特殊声明均为本站原创作品，转载时请注明作者和原文链接。


由于版权原因，请阅读原文 --> JDK 定时任务 Timer 与 ScheduledExecutorService 排坑记录

关注我们

作 者：haifeiWu
原文链接：https://www.hchstudio.cn/article/2018/b903/
版权声明：非特殊声明均为本站原创作品，转载时请注明作者和原文链接。

作 者：haifeiWu
原文链接：https://www.hchstudio.cn/article/2018/b903/
版权声明：非特殊声明均为本站原创作品，转载时请注明作者和原文链接。

正在认真敲代码的楼主，突然收到数据维护系统发过来的报警邮件说楼主凌晨跑的定时任务没有成功，于是便开始了楼主今天的找坑填坑的过程。

定时任务，关于 Timer 与 ScheduledExecutorService 的抉择

这事肯定会有小伙伴说了为啥不用Quartz啊，因为楼主的庙小啊，就几个定时任务而已Quartz太重了。

Timer 存在的问题

Timer的主要问题在于，如果TimerTask抛出未检查的异常，Timer将会产生无法预料的行为。Timer线程并不捕获异常，所以TimerTask抛出的未检查的异常会终止timer线程，这种情况下，Timer也不会再重新恢复线程的执行了;它错误的认为整个Timer都被取消了。此时，已经被安排但尚未执行的TimerTask永远不会再执行了，新的任务也不能被调度了。

使用 ScheduledExecutorService

ScheduledExecutorService 是 JDK 1.5之后 concurrent 包下提供的 API 。ScheduledExecutorService 妥善地处理了这个异常的任务，所以说在 JDK1.5 或更高的 JDK 中，楼主不建议使用Timer。关于 ScheduledExecutorService 楼主的另一篇文章也有提到，感兴趣的小伙伴请移步Java实现终止线程池中正在运行的定时任务

产生的问题

上面说了一堆 Timer 与 ScheduledExecutorService 的区别，有点不着重点，现在重点来了，楼主凌晨的定时任务没有跑成功就是使用了 ScheduledExecutorService 而不是 Timer ，当然倘若使用了Timer而导致的问题楼主也没必要说了。下面开始我们的找坑过程

查日志

通过 JDK 提供的 jstack 工具获取服务的 jstack 日志，如下所示：

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99

2018-07-18 15:39:09
Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode):

"Attach Listener" daemon prio=10 tid=0x00007f5bd0007800 nid=0x4e78 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"DestroyJavaVM" prio=10 tid=0x00007f5bec008800 nid=0x1dd5 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"Thread-4" prio=10 tid=0x00007f5bec4be000 nid=0x1df8 runnable [0x00007f5be88b2000]
   java.lang.Thread.State: RUNNABLE
	at java.net.PlainDatagramSocketImpl.receive0(Native Method)
	- locked <0x00000000e7e450b8> (a java.net.PlainDatagramSocketImpl)
	at java.net.AbstractPlainDatagramSocketImpl.receive(AbstractPlainDatagramSocketImpl.java:146)
	- locked <0x00000000e7e450b8> (a java.net.PlainDatagramSocketImpl)
	at java.net.DatagramSocket.receive(DatagramSocket.java:816)
	- locked <0x00000000e7e450e8> (a java.net.DatagramPacket)
	- locked <0x00000000e7e45110> (a java.net.DatagramSocket)
	at com.yg84.chelaile.middleware.common.remotedata.protocol.udp.UDPReceiver$1.run(UDPReceiver.java:55)
	at java.lang.Thread.run(Thread.java:745)

"pool-5-thread-1" prio=10 tid=0x00007f5bec4ba800 nid=0x1df6 waiting on condition [0x00007f5be89b3000]
   java.lang.Thread.State: TIMED_WAITING (parking)
	at sun.misc.Unsafe.park(Native Method)
	- parking to wait for  <0x00000000e7f1e510> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
	at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082)
	at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1090)
	at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
	at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)

"kafka-producer-network-thread | producer-1" daemon prio=10 tid=0x00007f5bec497000 nid=0x1df2 runnable [0x00007f5be8ffe000]
   java.lang.Thread.State: RUNNABLE
	at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
	at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
	at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79)
	at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87)
	- locked <0x00000000e7e45778> (a sun.nio.ch.Util$2)
	- locked <0x00000000e7e45788> (a java.util.Collections$UnmodifiableSet)
	- locked <0x00000000e7e45730> (a sun.nio.ch.EPollSelectorImpl)
	at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98)
	at org.apache.kafka.common.network.Selector.select(Selector.java:454)
	at org.apache.kafka.common.network.Selector.poll(Selector.java:277)
	at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:260)
	at org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:229)
	at org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:134)
	at java.lang.Thread.run(Thread.java:745)

"AsyncLoggerConfig-1" daemon prio=10 tid=0x00007f5bec32a800 nid=0x1dee waiting on condition [0x00007f5bf04c2000]
   java.lang.Thread.State: WAITING (parking)
	at sun.misc.Unsafe.park(Native Method)
	- parking to wait for  <0x00000000e7638090> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
	at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
	at com.lmax.disruptor.BlockingWaitStrategy.waitFor(BlockingWaitStrategy.java:45)
	at com.lmax.disruptor.ProcessingSequenceBarrier.waitFor(ProcessingSequenceBarrier.java:55)
	at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:123)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)

"Service Thread" daemon prio=10 tid=0x00007f5bec0b3800 nid=0x1ddc runnable [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"C2 CompilerThread1" daemon prio=10 tid=0x00007f5bec0b1000 nid=0x1ddb waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"C2 CompilerThread0" daemon prio=10 tid=0x00007f5bec0ae800 nid=0x1dda waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"Signal Dispatcher" daemon prio=10 tid=0x00007f5bec0ac800 nid=0x1dd9 runnable [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"Finalizer" daemon prio=10 tid=0x00007f5bec08c000 nid=0x1dd8 in Object.wait() [0x00007f5bf163a000]
   java.lang.Thread.State: WAITING (on object monitor)
	at java.lang.Object.wait(Native Method)
	- waiting on <0x00000000e74a07a0> (a java.lang.ref.ReferenceQueue$Lock)
	at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
	- locked <0x00000000e74a07a0> (a java.lang.ref.ReferenceQueue$Lock)
	at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
	at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209)

"Reference Handler" daemon prio=10 tid=0x00007f5bec08a000 nid=0x1dd7 in Object.wait() [0x00007f5bf173b000]
   java.lang.Thread.State: WAITING (on object monitor)
	at java.lang.Object.wait(Native Method)
	- waiting on <0x00000000e74a0848> (a java.lang.ref.Reference$Lock)
	at java.lang.Object.wait(Object.java:503)
	at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
	- locked <0x00000000e74a0848> (a java.lang.ref.Reference$Lock)

"VM Thread" prio=10 tid=0x00007f5bec085800 nid=0x1dd6 runnable 

"VM Periodic Task Thread" prio=10 tid=0x00007f5bec0b7000 nid=0x1ddd waiting on condition 

JNI global references: 165

通过 jstack 日志并没有发现线程死锁，并且也看到楼主开启的 ScheduledThreadPoolExecutor 也在正常运行，并没有发现问题。

1
2
3
4
5
6
7
8
9
10
11
12
"pool-5-thread-1" prio=10 tid=0x00007f5bec4ba800 nid=0x1df6 waiting on condition [0x00007f5be89b3000]
   java.lang.Thread.State: TIMED_WAITING (parking)
	at sun.misc.Unsafe.park(Native Method)
	- parking to wait for  <0x00000000e7f1e510> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
	at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082)
	at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1090)
	at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
	at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)

扒源码

因为出问题的是定时任务没有执行，所以楼主打算看一下 ScheduledExecutorService 下 scheduleAtFixedRate 代码

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

/**
     * Creates and executes a periodic action that becomes enabled first
     * after the given initial delay, and subsequently with the given
     * period; that is executions will commence after
     * {@code initialDelay} then {@code initialDelay+period}, then
     * {@code initialDelay + 2 * period}, and so on.
     * If any execution of the task
     * encounters an exception, subsequent executions are suppressed.
     * Otherwise, the task will only terminate via cancellation or
     * termination of the executor.  If any execution of this task
     * takes longer than its period, then subsequent executions
     * may start late, but will not concurrently execute.
     *
     * @param command the task to execute
     * @param initialDelay the time to delay first execution
     * @param period the period between successive executions
     * @param unit the time unit of the initialDelay and period parameters
     * @return a ScheduledFuture representing pending completion of
     *         the task, and whose {@code get()} method will throw an
     *         exception upon cancellation
     * @throws RejectedExecutionException if the task cannot be
     *         scheduled for execution
     * @throws NullPointerException if command is null
     * @throws IllegalArgumentException if period less than or equal to zero
     */
    public ScheduledFuture<?> scheduleAtFixedRate(Runnable command,
                                                  long initialDelay,
                                                  long period,
                                                  TimeUnit unit);

果不其然，通过这个方法的 doc 中下面的这段话，大概可以知道任务遇到异常的时候，这个任务就不再执行。当然其他任务是不受影响的。

1
If any execution of the task encounters an exception, subsequent executions are suppressed. Otherwise, the task will only terminate via cancellation or termination of the executor.  If any execution of this task takes longer than its period, then subsequent executions may start late, but will not concurrently execute.

复盘

根据楼主上面的分析过程，可以知道导致出问题的原因就是代码中抛出了非受检异常，下面是楼主的测试代码，代码很简单就是使用 ScheduledExecutorService 启动两个定时任务，其中一个抛出空指针异常线程不捕获。

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48

public class TestCase {

	public static void main (String[] args) {
		ScheduledExecutorService service = Executors
				.newSingleThreadScheduledExecutor();
		service.scheduleAtFixedRate(new TestJob(), 0, 1000, TimeUnit.MILLISECONDS);
		service.scheduleAtFixedRate(new TestJob2(), 0, 1000, TimeUnit.MILLISECONDS);
	}

	static class TestJob implements Runnable {

		int count = 0;

		public TestJob() {

		}

		@Override
		public void run() {
//			try {
				count++;
				System.out.println("TestJob count : " + count);
				if (count == 5) {
					throw new NullPointerException();
				}
//			} catch (Exception e) {
//				e.printStackTrace();
//			}
		}
	}

	static class TestJob2 implements Runnable {

		int count = 0;

		public TestJob2() {

		}

		@Override
		public void run() {
			count++;
			System.out.println("TestJob2 count : " + count);
		}
	}

}

代码运行结果：在 TestJob 抛出异常后不再执行，TestJob2 不受影响可以继续执行。

运行结果

问题解决

问题产生的根源找到了，解决起来就比较简单了，具体代码如下所示

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

static class TestJob implements Runnable {

		int count = 0;

		public TestJob() {

		}

		@Override
		public void run() {
			try {
				count++;
				System.out.println("TestJob count : " + count);
				if (count == 5) {
					throw new NullPointerException();
				}
			} catch (Exception e) {
				e.printStackTrace();
			}
		}
	}

小结

总的来看这个问题也比较简单，相对来说比较隐蔽一些。当然，跟自己平时编码规范关系很大。

关注我们

作 者：haifeiWu
原文链接：https://www.hchstudio.cn/article/2018/b903/
版权声明：非特殊声明均为本站原创作品，转载时请注明作者和原文链接。

分享
Java
聊聊 JDK 阻塞队列源码（ReentrantLock实现）Dagger Android支持库（译文）
微信关注我们
分类
  • Android8
  • Go3
  • Java58
  • Kafka,Java1
  • Kotlin2
  • MapReduce1
  • Python2
  • Raft1
  • Redis1
  • ThreadPoolExecutor1
  • 工具1
  • 总结7
  • 旅游日记1
标签
MySQL ChanghuiN Android haifeiWu Java 译文 Docker Spring Boot 源码解析 设计模式 工具 web hexo 学习笔记 Kotlin 算法 总结 netty Redis Python WebFlux 性能测试 golang 配置中心 Nginx 性能优化 旅游日记 Raft Shell 散列表 源码 问题排查
最近文章
  • 基于Redis的分布式锁到底安全吗？
  • 【译】Raft 学生指南
  • ThreadPoolExecutor 的简单梳理
  • MapReduce 的简单实现
  • 使用 Map 实现策略模式
  • 使用 Go 优化我们的接口
  • 如何使用 Redis 实现分布式锁
  • Kafka Consumer 的 Rebalance 机制
  • 实时数据并发写入 Redis 优化
  • Redis 与 Lua 使用中的小问题
福利专区
    免费SSL证书
      阿里云红包
        腾讯云专属福利
        Copyright © 2020 代码星冰乐. Powered by ChanghuiN. 版权所有 晋ICP备15001365号
        特别感谢： 云服务器服务商 、 CDN 服务商