Fix deadlock on close() with congested server.

David Pratt · David Pratt · commit 74066327ce15 · 2015-04-23T12:17:01.000-05:00
The RPC call for close() should not necessarily listen indefinitely,
since it will block essentially forever if the server is congested.
diff --git a/src/com/rabbitmq/client/impl/ChannelN.java b/src/com/rabbitmq/client/impl/ChannelN.java
@@ -571,7 +571,9 @@ public AMQCommand transformReply(AMQCommand command) {
             // we wait for the reply. We ignore the result.
             // (It's NOT always close-ok.)
             notify = true;
-            k.getReply(-1);
+			// Should not wait indefinately, since if the server is congested
+			// the call will lock and never return. This stalls and kills the current thread.
+            k.getReply(10000);
         } catch (TimeoutException ise) {
             // Will never happen since we wait infinitely
         } catch (ShutdownSignalException sse) {
