Many thanks.
On Wed, Aug 19, 2020, 11:11 AM Cliff Jansen wrote:
> There is nothing wrong with your current strategy. You could
> alternatively create a new connection on the same proactor instance.
> You can also reuse a connection with a new transport, for example by
> calling pn_proactor_rele
There is nothing wrong with your current strategy. You could
alternatively create a new connection on the same proactor instance.
You can also reuse a connection with a new transport, for example by
calling pn_proactor_release_connection() when you get the
PN_TRANSPORT_CLOSED event and before call
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 l
