Alexandre Dutra 2ff8973f69 Allow blocking calls inside HashedWheelTimer start() and stop() (#10810) ... Motivation: When a HashedWheelTimer instance is started or stopped, its working thread is started or stopped. These operations block the calling thread: - start() calls java.util.concurrent.CountDownLatch.await() to wait for the worker thread to finish initializing; - stop() calls java.lang.Thread.join(long) to wait for the worker thread to exit. BlockHound detects these calls and as a consequence, prevents HashedWheelTimer from working properly, if it is started or stopped in a thread that is not allowed to block. Modifications: Added two more BlockHound exceptions to io.netty.util.internal.Hidden.NettyBlockHoundIntegration: one for HashedWheelTimer.start() and one for HashedWheelTimer.stop(). Result: HashedWheelTimer can now be started and stopped properly when BlockHound is activated.		2020-11-23 08:41:07 +01:00
..
src	Allow blocking calls inside HashedWheelTimer start() and stop() (#10810)	2020-11-23 08:41:07 +01:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2020-11-11 05:47:51 +00:00