On Mon, 2017-01-02 at 14:01 -0700, dominate wrote: > I start my default container: proton::default_container > I have a idle timeout and after that time, correctly > on_transport_close > event is called. > But then, nothing !! > What should I do? > How can i reconnect, especially, manually? > In on_transport_close I tried to stop container, but nothing happens:
Do you mean that the process hung? If so this is a known bug in previous versions of proton-c. It should be fixed in 0.16. However you don't need to close the container to reconnect, and in fact it doesn't really make much sense. For the vast majority of client applications you create a single container for the entire lifetime of the application itself. All you should need to do is to respond to on_connection_close by rerunning the same connect that you did originally. You will probably want to schedule this connect in the future to avoid busy looping. There is currently no automatic way to handle these reconnects, but it is something we will be looking at soon. Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
