Commit 0d687ec
committed
fix: propagate runAsync dispatch failure into retryFuture
If ForkJoinPool.commonPool() rejects the retry task (e.g. during JVM
shutdown), the runAsync future completes exceptionally but retryFuture
was never completed, causing the overall request future to hang. Wire
an .exceptionally() handler on the runAsync future so any dispatch
failure propagates into retryFuture immediately.1 parent d1c52e0 commit 0d687ec
1 file changed
Lines changed: 12 additions & 7 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
321 | 321 | | |
322 | 322 | | |
323 | 323 | | |
324 | | - | |
325 | | - | |
326 | | - | |
327 | | - | |
328 | | - | |
329 | | - | |
330 | | - | |
| 324 | + | |
| 325 | + | |
| 326 | + | |
| 327 | + | |
| 328 | + | |
| 329 | + | |
| 330 | + | |
| 331 | + | |
| 332 | + | |
| 333 | + | |
| 334 | + | |
| 335 | + | |
331 | 336 | | |
332 | 337 | | |
333 | 338 | | |
| |||
0 commit comments