Hi
Is it a trouble of DBViewer?
Will you become the same phenomenon other DataBase FrontEnd?(ex DTP)
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.
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.
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.