From 5cd7d4b442fb8552e3ce032e3a788fd0d52261da Mon Sep 17 00:00:00 2001 From: Martin Ritchie Date: Mon, 22 Jan 2007 16:47:06 +0000 Subject: QPID-308 Configurable timeout on blockForFrame. Stopping on InterruptedException is not correct logic. git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk/qpid@498690 13f79535-47bb-0310-9956-ffa450edef68 --- .../qpid/client/protocol/BlockingMethodFrameListener.java | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'java/client/src') diff --git a/java/client/src/main/java/org/apache/qpid/client/protocol/BlockingMethodFrameListener.java b/java/client/src/main/java/org/apache/qpid/client/protocol/BlockingMethodFrameListener.java index 1656695ba9..ff38b96e63 100644 --- a/java/client/src/main/java/org/apache/qpid/client/protocol/BlockingMethodFrameListener.java +++ b/java/client/src/main/java/org/apache/qpid/client/protocol/BlockingMethodFrameListener.java @@ -119,11 +119,11 @@ public abstract class BlockingMethodFrameListener implements AMQMethodListener catch (InterruptedException e) { // IGNORE -- //fixme this isn't ideal as being interrupted isn't equivellant to sucess - if (!_ready && timeout != -1) - { - _error = new AMQException("Server did not respond timely"); - _ready = true; - } +// if (!_ready && timeout != -1) +// { +// _error = new AMQException("Server did not respond timely"); +// _ready = true; +// } } } } -- cgit v1.2.1