On Jan 10, 2008 3:47 PM, David Durham, Jr. <email@example.com> wrote:
> How difficult would it be to change SQuirreL's session disconnect
> behavior such that it starts a disconnect thread with a timeout? I
> have a situation where I'll disconnect from a vpn before I close the
> my SQuirreL SQL session. The entire tool will freeze for, presumably,
> the OS socket timeout, which can be quite a long time. I'm using
> 2.6.1, so maybe this has been fixed. Haven't gotten around to
> updating yet :).
It's a bug, and you should file a bug report. Specifically,
SessionInternalFrame, when receiving an internalFrameClosing event,
calls SessionManager.closeSession on the event dispatch thread which
calls session.close(), which eventually closes the connection. Since
this can take a long time, it would be good to move this off of the
EDT. It's tricky though, as in the case where we are shutting down -
the exit should be delayed until all sessions are closed, and ideally
a dialog should allow the user to cancel the close for sessions that
are taking a long time to close.
Log in to post a comment.