On 01/07/2012 01:26 AM, Tom M wrote:
I’ve created a simpler test client (based on our deployed application)
to test this problem.
I ran your test client against the same package versions you listed for
qpidd and the client lib. I didn't pull a cable (as I was testing on
remote boxes) but instead issues a kill -STOP against the broker which
should be similar from the perspective of the client (i.e. it will miss
two heartbeats and abort the connection).
However in all my attempts it did correctly detect the closed connection
and issue an exception. The output was of the following form:
01_12 15:51:34 TstConn: sending msg: 45
01_12 15:51:34 TstConn: msg sent
01_12 15:51:35 TstConn: sending msg: 46
01_12 15:51:35 TstConn: msg sent
2012-01-12 10:51:35 warning Connection [42787 mrg11:5672] closed
01_12 15:51:36 TstConn: connection_.isOpen() detected lost connection
note: detected with isOpen() call, not an exception....
01_12 15:51:36 TstConn: sending msg: 47
01_12 15:51:36TstConn: qpid::Exception: Connection [42787 mrg11:5672] closed
...waiting on user (allow user to reconnect cable, so can attempt to close
connection on broker)
To continue shutdown, enter: 1
This is the same whichever size I choose. Would you mind verifying if
you see your problem with a kill -STOP in place of the network cable
removal? If not, I'll try and get a setup to test on where i can pull a
physical cable; if you can then it confirms there is something else
different in our test setup.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
