In some rare cases application stops and starts again

[killdashnine]

This happens because the start() method clears the pid before synchronizing the enabled state to the database, due to Play!'s transaction structure. A possible work-around would be to make the job scheduler clear the pid when an application has the enabled status.

[killdashnine]

In production mode with 8 cores this still seems to happen, reopening

[killdashnine]

14:58:04,380 INFO ~ Process: xeurobellen.git-status has stopped with exit value: 0 keep: false
14:58:04,393 INFO ~ Started xeurobellen.git
14:58:04,393 INFO ~ Removed kept pid: xeurobellen.git-start
14:58:04,524 INFO ~ It appears xeurobellen.git (PID: xeurobellen.git-start) is running while it should not

[killdashnine]

This seems to be very spurious, haven't seen it since....