Menu

#56 Quick successive restarts lose saved state

release_0.2
fixedawaitingtest
Java code (21)
7
2012-08-07
2012-03-14
No

If the scoreboard is started and then immediately (or within a few seconds) stopped, then when restarted it does load an auto-save xml file, but that file does not appear to have the actual previous state; everything is reset to internal defaults (e.g. all clocks count up, max time of 60 min, etc).

Discussion

  • Dan Streetman

    Dan Streetman - 2012-03-14

    Looks like the very first auto-save file contains internal defaults, only the second (and later) auto-save files contain the correct auto-loaded settings.

     
  • Dan Streetman

    Dan Streetman - 2012-03-14

    This was due to the delayed nature of event passing, as communication from the scoreboard back to XmlScoreBoard flow through helper Threads, as well as events flowing through Threads to XmlDocumentManagers.

    There is no way to know when all the initial changes have made their way back to the XmlScoreBoard, so instead AutoSaveScoreBoard is updated to defer backing up the auto-save files, and starting new auto-save, until after 10 seconds, which should be plenty of time for all scoreboard configuration to return to XmlScoreBoard (it should only realistically take a few milliseconds).

    Also changed the auto-save code to copy, instead of move, the existing auto-save files, so there is no window anymore where the auto-save xml may be lost if the scoreboard is stopped.

     
  • Dan Streetman

    Dan Streetman - 2012-08-07
    • status: pending --> fixedawaitingtest
     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB