[rhochmuth]

I've just added support for glacier2 in my application and all is working with the initial connection establishment. My client application has a disconnect and connect button . When the disconnect button is selected all the connections are explicitly close by invoking ice_connection()->close(true) on all the proxies. This works when not using a glacier2 router, but when the router is enabled it looks like close(..) closes the glacier2 session. If the connect button is then selected the client cannot re-connect back to the server.

Does this sound like the expected behaviour and is there a way to re-establish the router session and connection if close has been invoked on the proxies connection?

I've tried to do a few things, such as create a new router session again, but it doesn't appear to work. It seems like the router session needs to be created first, at least this is how all the examples are listed, and then the router is added to the adapter.

I've also removed all invocations of close(..), and this appears to work, but I'm not sure if there are some other issues with my application when doing this so I'll need to do some more experimenting. If I can't create a new session then is the only other alternative to not invoke close(...)?

Regards --Roland