Details
Description
As far as I can see its doing something as follows:
Timer triggers in SessionConnector, calls session.next()
checkSessionTime() returns false, calls session.reset() -> session.disconnect()
disconnect() calls responder.disconnect(), closes TCP session
I think session.next() perhaps needs changing when checkSessionTime is false to generate a logout message rather than calling reset(), unless there's another timer somewhere meant to do that which might have missed.
Reported by Toby Shepheard