Backend Connect timeout too short #38
Description
We're using ESR Automate as a backend to RText plugin.
The RText plugin worked fine as long as we had node-locked Automate licenses. With floating licenses it lakes longer than 5 seconds to start Automate backend, i.e. time between process start and printing of "listening at port xxx message". Which causes CliBackendStarter#getPort to throw a TimeoutException and the whole thing is aborted.
I increased the timeout org.rtext.lang.util.Wait.DEFAULT_TIMEOUT to 50 s, and got this working.
Kindly consider increasing the timeout in master.