Added one further test: The bindings are arranged in a different order. As a result, we get to A first directly from C, thus the lookup for A will work, and A isn't deleted. Then we later come back to A from C via B, thus the lookup for A still works, and then A is deleted. Hence we hit the bottom case of rabbit_binding:anything_but/3

Author: Matthew Sackman

test/src/com/rabbitmq/client/test/functional/ExchangeExchangeBindingsAutoDelete.java

@@ -113,5 +113,18 @@ public void testRepeatedTargetAutoDelete() throws IOException {
         assertExchangesNotExist(exchanges);
         assertExchangeNotExists("Source");
     }
+    
+    /*
+     * build (A -> B) (B -> C) (A -> C). Delete C and they should all vanish
+     */
+    public void testAutoDeleteBindingToVanishedExchange() throws IOException {
+        String[] exchanges = new String[] {"A", "B", "C"};
+        declareExchanges(exchanges);
+        channel.exchangeBind("C", "B", "");
+        channel.exchangeBind("B", "A", "");
+        channel.exchangeBind("C", "A", "");
+        channel.exchangeDelete("C");
+        assertExchangesNotExist(exchanges);
+    }
 
 }