#1375
- Created on2015-01-23 13:33
- Reported by
- StatusDuplicate
- PriorityNormal (3)
- Assigned to
- Milestone-
- Plan Level-
- EstimateNone/Small/Medium/Large Small
- Due Date-
Erlide Erlang nodes die when Windows host resumes from standby
Hi,
On my Windows 7 laptop I have consistently the problem that both Erlide Erlang nodes die (or appear to be down to Erlide) when I wake up the laptop from standby, which means that I have to restart Eclipse.
Is this a known problem that generally affects users that put their PCs in stanby with a running Eclipse+Erlide instance?
I guess the root cause for this problem lies in Erlang itself, but I wonder if their is no way for Erlide to detect the situation and restart the lost Erlang nodes automatically?
Details:
Eclipse IDE for C/C++ Developers 4.4.1.20140925-1820 epp.package.cpp null
Erlang language tools IDE 0.29.8.201412161411 org.erlide.feature.group Erlide project
Erlang R16B03-1 (erts-5.10.4) [64-bit] [smp:4:4] [async-threads:10]
Eshell V5.10.4 (abort with ^G)
On my Windows 7 laptop I have consistently the problem that both Erlide Erlang nodes die (or appear to be down to Erlide) when I wake up the laptop from standby, which means that I have to restart Eclipse.
Is this a known problem that generally affects users that put their PCs in stanby with a running Eclipse+Erlide instance?
I guess the root cause for this problem lies in Erlang itself, but I wonder if their is no way for Erlide to detect the situation and restart the lost Erlang nodes automatically?
Details:
Eclipse IDE for C/C++ Developers 4.4.1.20140925-1820 epp.package.cpp null
Erlang language tools IDE 0.29.8.201412161411 org.erlide.feature.group Erlide project
Erlang R16B03-1 (erts-5.10.4) [64-bit] [smp:4:4] [async-threads:10]
Eshell V5.10.4 (abort with ^G)
Leave a comment
on 2015-01-23 13:42 *
By Vlad Dumitrescu
Assigned to set to Vlad Dumitrescu
Status changed from New to Ongoing
Assigned to set to Vlad Dumitrescu
Status changed from New to Ongoing
You are correct in guessing it's not a problem specific to erlide. Any long-living TCP connection dies when PC goes to sleep and the TCP keepalive timeout is reached. See for example http://stackoverflow.com/questions/10665267/keep-ssh-session-alive-while-computer-sleep.
And you are also right that we could restart the backends. There can be inconsistencies if the PC went to sleep in a bad moment, but it's probably a low probability for it to happen in practice. I don't remember at the moment if there is anything that would prevent restarting.
I will look at that and fix it. Thanks for the report!
And you are also right that we could restart the backends. There can be inconsistencies if the PC went to sleep in a bad moment, but it's probably a low probability for it to happen in practice. I don't remember at the moment if there is anything that would prevent restarting.
I will look at that and fix it. Thanks for the report!
on 2015-01-23 13:49 *
By Vlad Dumitrescu
Status changed from Ongoing to Duplicate
Status changed from Ongoing to Duplicate