If a query is executed against a connection that was dropped due to inactivity, the progress dialog cannot be canceled in a timely way. It takes a very long time for myeclipse to regain control and execute the cancel request.
I expect the behaviour should be for myeclipse to reconnect to the database, before attempting to execute the query.