There seems to be a problem related to the ReconnectTimer. For a 2911 router (see below for version) we have experienced TLS disconnect problems. When trying to isolate and maybe to circumvent the problem, we have activated the reconnect timer functionality as suggested.
We are now experiencing a problem where a TLS session remains stuck in the Authenticated state:
R1#show onep session all
ID Username State ReconnectTimer ConnectTime ApplicationName
7250 cisco Authenticated 60 Wed Aug 27 22:05:51.608 test.app
The onep application itself is terminated (and hence the TCP connection to the router is also terminated), but on the router side the session is not timed out and cleaned up, as expected.
The reconnect functionality has now made the situation more difficult:
the router keeps the state associated with the session
the onep application can not be restarted with the same name
changing the application name allows a new connection to be established, but dpss functionality is blocked due to the state kept by the router for the stuck session
It seems like the ReconnectTimer is stuck, as the state has not transitioned to the Connected state. Might that be the case?