Looly
|
c008d0a081
|
prepare 5.4.6
|
2020-10-18 13:38:32 +08:00 |
|
Looly
|
756f9b3f87
|
release 5.4.5
|
2020-10-18 13:27:38 +08:00 |
|
Looly
|
7c23aadb9e
|
prepare 5.4.5
|
2020-09-30 12:04:01 +08:00 |
|
Looly
|
7038498add
|
release 5.4.4
|
2020-09-30 11:42:40 +08:00 |
|
Looly
|
50134d8822
|
add reader
|
2020-09-26 02:22:34 +08:00 |
|
Looly
|
4c12094a7f
|
fix code
|
2020-09-25 22:34:45 +08:00 |
|
Looly
|
479c4837c8
|
prepare 5.4.4
|
2020-09-18 16:55:15 +08:00 |
|
Looly
|
870ea9a329
|
release 5.4.3
|
2020-09-18 15:57:15 +08:00 |
|
Looly
|
0863461a18
|
prepare 5.4.3
|
2020-09-09 17:23:46 +08:00 |
|
Looly
|
2212ee7705
|
release 5.4.2
|
2020-09-08 20:59:52 +08:00 |
|
Looly
|
6d21bb930e
|
fix lock
|
2020-08-29 17:51:50 +08:00 |
|
zhuqianchao
|
0e9909ffeb
|
1. 在使用阻塞等待获取锁的方式中,必须在try代码块之外,并且在加锁方法与try代码块之间没有任何可能抛出异常的方法调用,避免加锁成功后,在finally中无法解锁。
说明一:如果在lock方法与try代码块之间的方法调用抛出异常,那么无法解锁,造成其它线程无法成功获取锁。
说明二:如果lock方法在try代码块之内,可能由于其它方法抛出异常,导致在finally代码块中,unlock对未加锁的对象解锁,它会调用AQS的tryRelease方法(取决于具体实现类),抛出IllegalMonitorStateException异常。
说明三:在Lock对象的lock方法实现中可能抛出unchecked异常,产生的后果与说明二相同。 java.concurrent.LockShouldWithTryFinallyRule.rule.desc
2. 补上遗漏的Override注解
|
2020-08-29 17:22:36 +08:00 |
|
Looly
|
50c30259cb
|
prepare 5.4.2
|
2020-08-29 15:25:30 +08:00 |
|
Looly
|
3ffffe3d3b
|
release 5.4.1
|
2020-08-29 15:07:08 +08:00 |
|
Looly
|
5be24863d1
|
prepare 5.4.1
|
2020-08-16 13:06:13 +08:00 |
|
Looly
|
2edf6f65cc
|
release 5.4.0
|
2020-08-16 12:10:34 +08:00 |
|
Looly
|
c47272922b
|
fix comment
|
2020-08-01 23:19:29 +08:00 |
|
Looly
|
04917da6e2
|
nio enhancement
|
2020-08-01 18:58:44 +08:00 |
|
Looly
|
baa8ddd9ed
|
prepare 5.3.11
|
2020-07-23 18:21:00 +08:00 |
|
Looly
|
1f19a31c5a
|
release 5.3.10
|
2020-07-23 18:07:43 +08:00 |
|
Looly
|
fb2596b6c7
|
prepare 5.3.10
|
2020-07-12 13:00:02 +08:00 |
|
Looly
|
8236ae61f2
|
release 5.3.9
|
2020-07-12 12:28:17 +08:00 |
|
Looly
|
01f19daa66
|
prepare 5.3.9
|
2020-06-17 15:34:36 +08:00 |
|
Looly
|
ceb8f868f2
|
release 5.3.8
|
2020-06-17 02:16:27 +08:00 |
|
Looly
|
94335d176b
|
add gif
|
2020-06-05 17:59:00 +08:00 |
|
Looly
|
9ca7d93f70
|
prepare 5.3.8
|
2020-06-03 18:51:56 +08:00 |
|
Looly
|
78f57d7ffd
|
release 5.3.7
|
2020-06-03 18:48:35 +08:00 |
|
Looly
|
8e2f63d576
|
fix bugs
|
2020-06-03 18:15:33 +08:00 |
|
Looly
|
0b74d3769d
|
prepare 5.3.7
|
2020-05-31 18:00:07 +08:00 |
|
Looly
|
62e02e877a
|
release 5.3.6
|
2020-05-31 17:30:02 +08:00 |
|
Looly
|
5e381a1007
|
prepare 5.3.6
|
2020-05-14 02:19:43 +08:00 |
|
Looly
|
3da83e0227
|
release 5.3.5
|
2020-05-13 21:22:54 +08:00 |
|
Looly
|
58fab104c7
|
prepare 5.3.5
|
2020-05-10 08:50:33 +08:00 |
|
Looly
|
c2d70a4613
|
release 5.3.4
|
2020-05-10 00:14:29 +08:00 |
|
Looly
|
fdf735fa05
|
prepare 5.3.4
|
2020-05-06 08:24:09 +08:00 |
|
Looly
|
513fb1c861
|
release 5.3.3
|
2020-05-05 23:24:00 +08:00 |
|
Looly
|
63732834ac
|
CronPattern support L
|
2020-04-25 19:23:42 +08:00 |
|
Looly
|
669d19eab8
|
prepare 5.3.3
|
2020-04-23 15:20:05 +08:00 |
|
Looly
|
d6125c1bf7
|
release 5.3.2
|
2020-04-23 14:31:42 +08:00 |
|
Looly
|
ae13d262b0
|
fix comment
|
2020-04-19 12:39:32 +08:00 |
|
Looly
|
8e42898d46
|
fix cron bug
|
2020-04-19 11:41:10 +08:00 |
|
Looly
|
d3e547515a
|
prepare 5.3.2
|
2020-04-17 18:33:24 +08:00 |
|
Looly
|
edd47d6c86
|
release 5.3.1
|
2020-04-17 18:15:22 +08:00 |
|
Looly
|
2034be3b5a
|
prepare 5.3.1
|
2020-04-11 14:30:43 +08:00 |
|
Looly
|
97ad2fbf08
|
release 5.3.0
|
2020-04-11 14:09:07 +08:00 |
|
Looly
|
bc486cdac4
|
fix code
|
2020-04-11 13:08:46 +08:00 |
|
Looly
|
6b13cb5263
|
prepare 5.3.0
|
2020-04-04 00:50:44 +08:00 |
|
Looly
|
130fa344c4
|
prepare 5.2.6
|
2020-03-27 00:31:35 +08:00 |
|
Looly
|
4d8b21f831
|
release 5.2.5
|
2020-03-26 23:58:44 +08:00 |
|
Looly
|
122f5be484
|
prepare 5.2.5
|
2020-03-22 18:16:41 +08:00 |
|