Reconnecting after network down time leaves two copies of node handler in memory.

ryanbressler / golem

Research Oriented Distributed Computing.

1 stars 1 forks source link

Reconnecting after network down time leaves two copies of node handler in memory. #50

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

Please use labels and text to provide additional information.

Original issue reported on code.google.com by ryanbres...@gmail.com on 22 May 2013 at 8:29