There seems to be state that is retained for a gopher application either by the controller or the worker, even after it has voted to halt. This is seen when using the same gopher deployment to run the same application twice, one after the other completes. An exception is thrown:
Jul 23, 2013 2:52:39 PM edu.usc.goffish.gopher.impl.ControlPellet invoke
SEVERE: Unexpected BSP Control Message. Invalid superstep seen: 0 when expecting superstep: 2
charithwiki
commented
11 years ago
There seems to be state that is retained for a gopher application either by the controller or the worker, even after it has voted to halt. This is seen when using the same gopher deployment to run the same application twice, one after the other completes. An exception is thrown: Jul 23, 2013 2:52:39 PM edu.usc.goffish.gopher.impl.ControlPellet invoke SEVERE: Unexpected BSP Control Message. Invalid superstep seen: 0 when expecting superstep: 2