Fixes [SUREFIRE-1516]: Forked JVM should not block in IO to read more…

… from the host JVM after it sends BYE_ACK. Threads blocking on `read` may not be interruptable until they poll for interrupts (every 350msec), which can introduce significant latency for short-lived processes.
apache · Nov 11, 2019 · 2fbe44f · 2fbe44f
1 parent b97df5a
commit 2fbe44f
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/surefire-api/src/main/java/org/apache/maven/surefire/booter/CommandReader.java b/surefire-api/src/main/java/org/apache/maven/surefire/booter/CommandReader.java
@@ -412,6 +412,10 @@ public void run()
                                 CommandReader.this.wakeupIterator();
                                 callListeners( command );
                                 break;
+                            case BYE_ACK:
+                                //After SHUTDOWN no more commands can come. Hence, do NOT go back to blocking in IO
+                                callListeners( command );
+                                return;
                             default:
                                 callListeners( command );
                                 break;