Hi, Just wondering if there is any feedback on this question. To summarise, in case it's unclear, ... When I detect loss of the underlying tcp connection in my sub-class of connection_driver, I notify the Qpid engine about this by calling either disconnected() or connection().close(). In either case, when I re-establish the tcp connection, I call connect() and dispatch() from within my connection_driver sub-class but nothing happens. Nothing appears in the output buffer.
Should that work OR is connection_driver for single use only? Thanks for any help. From: Tom Crowe Sent: Monday, November 6, 2023 4:07 PM To: users@qpid.apache.org Subject: RE: external event loop Hi, So all working fine with Connection_driver and an external event loop. However, when trying to add a 're-connect' feature, the connection_driver based client is unresponsive. Details: 1. When the server fails abruptly, the loss of transport is detected by a socket recv on the client. 2. Two different methods have been separated used to inform the Qpid engine about the situation - disconnected() and connection().close() 3. When the connection_driver detects a new transport connection, connect() and dispatch() are called, but nothing appears in the write buffer. Is connection_driver a 'one-time use only' class? If not, how can I use it to re-establish an amqp connection? Thanks.
