netty5

History

Chris Vest fd8c1874b4 Fix #10614 by making UnorderedTPEExecutor.scheduleAtFixedRate run tasks more than once (#10659 ) Motivation: All scheduled executors should behave in accordance to their API. The bug here is that scheduled tasks were not run more than once because we executed the runnables directly, instead of through the provided runnable future. Modification: We now run tasks through the provided future, so that when each run completes, the internal state of the task is reset and the ScheduledThreadPoolExecutor is informed of the completion. This allows the executor to prepare the next run. Result: The UnorderedThreadPoolEventExecutor is now able to run scheduled tasks more than once. Which is what one would expect from the API.	2020-10-14 11:09:16 +02:00
..
src	Fix #10614 by making UnorderedTPEExecutor.scheduleAtFixedRate run tasks more than once (#10659 )	2020-10-14 11:09:16 +02:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2020-10-13 06:29:26 +00:00

Fix #10614 by making UnorderedTPEExecutor.scheduleAtFixedRate run tasks more than once (#10659 )

Motivation:
All scheduled executors should behave in accordance to their API.
The bug here is that scheduled tasks were not run more than once because we executed the runnables directly, instead of through the provided runnable future.

Modification:
We now run tasks through the provided future, so that when each run completes, the internal state of the task is reset and the ScheduledThreadPoolExecutor is informed of the completion.
This allows the executor to prepare the next run.

Result:
The UnorderedThreadPoolEventExecutor is now able to run scheduled tasks more than once.
Which is what one would expect from the API.

2020-10-14 11:09:16 +02:00

src

Fix #10614 by making UnorderedTPEExecutor.scheduleAtFixedRate run tasks more than once (#10659 )

2020-10-14 11:09:16 +02:00

pom.xml

[maven-release-plugin] prepare for next development iteration

2020-10-13 06:29:26 +00:00