Likely fix for issue #42

On inturruption, the Command class is nulling the output. But this is causing the statemachine to not know what to do with the actual output it eventually gets. If we leave the output there, the RSM can still update the output, even though the client has moved on.
redis · Feb 27, 2015 · 3e20467 · 3e20467
1 parent bd5227f
commit 3e20467
Showing 1 changed file with 0 additions and 1 deletion.
diff --git a/src/main/java/com/lambdaworks/redis/protocol/Command.java b/src/main/java/com/lambdaworks/redis/protocol/Command.java
@@ -74,7 +74,6 @@ protected void interruptTask() {
 
         if (latch.getCount() == 1) {
             latch.countDown();
-            output = null;
         }
     }