Ticket #22717

Eclipse freezes for long when closing a broken connection

Eröffnet am: 2010-08-04 17:47 Letztes Update: 2010-09-01 13:21

Auswertung:
Verantwortlicher:
(Keine)
Typ:
Status:
Offen
Komponente:
(Keine)
Meilenstein:
(Keine)
Priorität:
5 - Mittel
Schweregrad:
5 - Mittel
Lösung:
Keine
Datei:
2

Details

Steps to reproduce: 1. In DBViewer, open a connection to a remote database

2. Disconnect from the internet (thus breaking the connection)

3. Right-click on the database and select Close

4. => the whole Eclipse is frozen, looking as a grey window with a title bar without any content for many minutes (more than 20), after that it becomes active again

Expected behavior: the connection should be closed immediately.

Eclipse & DBViewer versions:

Eclipse 3.4, DBViewer 1.2.1, JVM Sun 1.6.0.20, OS Linux - Ubuntu

Please let me know what other information aside of the attached thread dumps I can provide to help with this.

Ticket-Verlauf (3/7 Historien)

2010-08-04 17:47 Aktualisiert von: malyvelky
  • New Ticket "Eclipse freezes for long when closing a broken connection" created
2010-08-04 17:50 Aktualisiert von: malyvelky
  • Details Updated
2010-08-20 14:08 Aktualisiert von: zigen
Kommentar

Hi

Is it a trouble of DBViewer?

Will you become the same phenomenon other DataBase FrontEnd?(ex DTP)

2010-08-26 17:39 Aktualisiert von: malyvelky
Kommentar

This is indeed a very good question.

As suggested, I've tried to reproduce the problem with Eclipse 3.5.2 and its Database Development perspective using the Data Source Explorer. Again I opened a connection, disconnected the VPN connection to the database, and invoked Disconnect on the database. Again it took a very long time for the connection to close, which is bad, but Eclipse itself didn't freeze and I could use its other functionality without problems, which is good.

Conclusion: It is not unique to DBViewer that closing a database connection over an interrupted network connection takes very long time, but clearly it could be done without freezing Eclipse.

2010-09-01 13:21 Aktualisiert von: zigen
Kommentar

Hi,

The DB disconnection process changed to asynchronization process.

I think that you can do the disconnect processing smooth in the upcoming version.

It has committed to SVN.

Dateianhangliste

  • tmp2.txt(15KB)
    • Thread dump from one case when Eclipse was frozen
  • tmp.txt(26KB)
    • Thread dump from another case when Eclipse was frozen (produced by VisaulVM)

Bearbeiten

Please login to add comment to this ticket » Anmelden