#111 Quantum locks Eclipse on network fault

[Matt Hilliard]

All you need to do is kill the network connection between the database
and Quatnum mid-transaction (pulling a nic plug, killing a router,
whatever). I realize this doesn't cover "normal" operation, but almost all
network-based apps deal with this is some fashion, gracefully.

[Julen Parra]

Logged In: YES
user_id=180901

Thanks for your info. I'll try to setup Quantum to access a
remote database and will try to address the problem.

[Matt Hilliard]

Logged In: YES
user_id=969951

No worries.
If its more difficult to recreate than I think it is, or you need more details, just let
me know.

[Christian Sprajc]

Logged In: YES
user_id=587903
Originator: NO

Every Remote call should be execute in a SwingWorker. E.g. the executing of a Query (which might take very long). Otherwise Eclipse always gets locked!

[Julen Parra]

Logged In: YES
user_id=180901
Originator: NO

There is an option to execute queries as separate threads. It's not default as it gave extrange problems. Perhaps some JDBC drivers where not really multi-threaded, as they should, perhaps there was an error in the implementation. You can try the option (Window->Preferences->QuantumDB-> Run queries in separate threads ? ) to see if your experience is good. If not, please comment, as that is a long-standing problem of difficult testing. (Note that only long-running queries will display the "Run in background" dialog).