On 10/07/2013 09:38 AM, NeilOwens wrote:
Yes, I apply a 1 second heartbeat to the connection. We're currently seeing
a 4 second connection timeout (this is elapsed time within connection.open()
when the destination IP address doesn't exist). We don't really want to
have to post the connect to a different thread, so we're looking at other
options before we do that.
Hmm, I wonder why that is... I see the timeout firing after two seconds
as expected, e.g.
./src/tests/qpid-send --connection-options '{heartbeat:1}' --address abc
--broker <bad ip> --log-enable trace+
Gives:
2013-10-07 10:35:41 [Client] debug Created connection 192.56.0.111 with
{heartbeat:1}
2013-10-07 10:35:41 [Client] debug Starting connection, urls=[192.56.0.111]
2013-10-07 10:35:41 [Client] info Trying to connect to 192.56.0.111...
2013-10-07 10:35:41 [Client] debug Created IO thread: 0
2013-10-07 10:35:41 [Network] debug TCPConnector created for 0-10
2013-10-07 10:35:41 [Client] info Set TCP_NODELAY
2013-10-07 10:35:41 [System] info Connecting: 192.56.0.111:5672
2013-10-07 10:35:43 [Client] debug Traffic timeout
2013-10-07 10:35:43 [Network] warning Connect failed: Connection timedout
2013-10-07 10:35:43 [Client] warning Connection closed
2013-10-07 10:35:43 [System] debug Exception constructed: Connection closed
2013-10-07 10:35:44 [Client] info Failed to connect to 192.56.0.111: Connection
closed
qpid-send: Failed to connect (reconnect disabled)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
