Description
It takes 4 times longer to establish a session with Saros/I compared to Saros/E. (Saros/I 40 seconds, Saros/E 10 seconds)
Reproduction
Expected Behaviour
The constant part of the time it takes to establish a session should be at most 50% higher compared to Saros/E.
Remarks
As Stefan Rossbach pointed out, this is due to an internal connection timeout, which is 30 seconds long.
This timeout and the usual time it takes for Saros/E adds up to the time it takes Saros/I to establish a connection.
If you do not add more information like:
Used network configuration, network settings within Saros and add the log files
It is likely that this bug either:
You spent a long time testing and testing. I will not (and other developers as well) spend that time again to gather the required information.
Franz can you verify this ? E.g connecting done on the same system and connecting done between two different systems on the same network (local intranet) ?
Took 1 second to establish a session between a IntelliJ and a Eclipse client.
The same issue would apply to Eclipse as well which is not the case.
I can establish Socks5 sessions between IntelliJ <-> Eclipse without any problems.