qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gordon Sim <g...@redhat.com>
Subject Re: Idle timeout and Java client
Date Wed, 06 May 2009 10:40:54 GMT
Garrett Smith wrote:
> I'm running into some warnings when running the Java client:
>   WARN [org.apache.qpid.transport.ClientDelegate] Ignoring the idle
>   timeout 3600 set by the connection, using the brokers max value 0
> The source for this is here:
> http://svn.apache.org/viewvc/qpid/trunk/qpid/java/common/src/main/java/org/apache/qpid/transport/ClientDelegate.java?view=markup
> When the idle timeout from the broker is 0, you'll always get this
> warning (see the code).
> Apart from the fact that the warning will always complain when timeout
> is 0, I'm wondering about the idle timeout itself -- I'm not seeing a
> way to set that on the broker (C++ M4).
> I'm assuming that idle timeout of 0 means "never timeout", which is
> probably what I want anyway. Is there a way to configure this for the
> C++ broker?

Heartbeats were added after the M4 release and prior to that the broker 
always sent 0 as the max timeout.

On trunk and in the upcoming M5 release the broker does support sending 
heartbeats (I believe the maximum delay is a hard coded 120 seconds).

Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org

View raw message