After the Modeling service crashes, the
RUNNING_PIDfile in
./ModelServiceis not deleted, so Windows Services doesn't recognize that the Modeling service has stopped. Thus, you can no longer stop or restart the Modeling service from the Windows Services program.
The Modeling service crash depends on the machine's memory allocated to the Modeling service. For example, in a Windows machine with 16GB RAM, it takes about 120 open changesets in a few minutes to crash it.
You can run
stop.batmanually in command line (administrator mode) and then you should be able to refresh the correct status in Services and restart the Modeling service from Services again. The
stop.batfile can be found in
./ModelService/bin.