You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A thread dump taken before the failing assertion, shows just one of the threads still running:
"processor-1" #16 daemon prio=5 os_prio=0 tid=0x00007f56e0680000 nid=0x390b runnable [0x00007f5721c66000]
java.lang.Thread.State: RUNNABLE
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:312)
at reactor.core.publisher.WorkQueueProcessor$WorkQueueInner.run(WorkQueueProcessor.java:505)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1129)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:748)
Locked ownable synchronizers:
- <0x000000076d598d18> (a java.util.concurrent.ThreadPoolExecutor$Worker)
Reactor Core version
3.2.0.M1
JVM version (e.g. java -version)
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)
The text was updated successfully, but these errors were encountered:
Expected behavior
forceShutdown()
completely shutdowns its inner executor, leaving no threads from it runningActual behavior
One of the
WorkQueueProcessor
's inner executor threads keeps running afterforceShutdown()
, even after being interrupted.Steps to reproduce
This test (copied from
TopicProcessorTest
intoWorkQueuProcessorTest
) reproduces the behavior:A thread dump taken before the failing assertion, shows just one of the threads still running:
Reactor Core version
3.2.0.M1
JVM version (e.g.
java -version
)java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)
The text was updated successfully, but these errors were encountered: