Hi,

I have a C app using Proton-C and it is connected to an AMQP provider.
Periodically, the AMQP provider is closing the connection and I need to
reconnect (my app is supposed to run, ideally, 24/7).

Currently, I handle this by simply catching the related transport events in
the Proactor event loop and then, when I get those errors, I free the
proactor, free the AMQP message and then go back to the initial Proactor
loop .... similar behavior as it happens when the program first starts. It
works.

My question is: is there any best practice to handle a reconnect, less
invasive than just freeing the Proactor and starting from scratch ?

Additionally, is there a way so I reconnect and also keep my link objects
and "reuse" / "re-attach" them after the reconnect ?

Many thanks,
Adrian

Reply via email to