Working with an environment under proxy can be tricky. If the Eclipse has the network configuration set to use the NATIVE proxy settings, when trying to connect to a QEMU machine on localhost will give hang Eclipse until the timeout since the QEMU address is not added to the "No proxy" list. The timeout is too long and Eclipse is blocked until the timeout. tested in kepler: f1fc72a31f7e51364ba3bccf45c028e694aefb9a
Keep in mind this is an upstream eclipse bug not YP per say
When trying to reproduce the reported issue, I've found that current Eclipse versions (tested Kepler, Luna and Mars) show the expected behavior, that is, to time out when attempting a remote connection that is not available, but the application does no hang anymore (you can continue work) and the default timeout is 60 seconds (then a message is displayed). My guess is that a patch was implemented at some point in Eclipse to attempt the remote connection on a different thread, thus avoiding unresponsiveness. I will look for such patch. In the meantime, I would rather close this bug as won't fix. Any objections?
Waiting For Upstream status is being removed, changing to Accepted.
Chin Huat - could you double-check this and see if you think we should close it?
Created attachment 4274 [details] SSH timeout setting in C/C++ Remote Application launch As of Eclipse Photon release (which we will be upgrading to very soon), it is now possible to configure SSH timeout for C/C++ Remote Application launch, see screenshot attached. I've also verified that by default the SSH connection will timeout almost immediately, the default timeout value is set to 0 seconds.
Stay tuned for YP 2.6 Eclipse upgrade.