#602 sesion disconnect network timeout freezes UI

open
nobody
None
5
2012-12-29
2008-01-11
David Durham
No

On Jan 10, 2008 3:47 PM, David Durham, Jr. <david.durham.jr@gmail.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.

Rob

Discussion

  • I experience the same/similar problem (running OpenSuse 10.3 - Squirrel version 2.6.5a).

    In my case the program will freeze for ages when the connection with the database has timed out. When doing a Session > Refresh or when closing the program Squirrel just freezes. When the connection with the database hasn't timed out yet I can just refresh the session or close the program without a problem.

    Eelco.

     
  • This still appears to be a problem in v3.2.1... I'm also using the client over a vpn and when I have minor hiccups on the vpn (which most other programs, like rdesktop can recover from) my session always freezes for about 10 minutes.

     
  • Guus
    Guus
    2011-03-21

    I'm bugged by the same issue. After suspending my laptop, it takes up to a couple of minutes to close each open session in SquirrelSQL. It's annoying.

     
  • This still appears to be a problem in v3.3.0.