On Windows platform, the container does not stop the server
Expected Behaviour
Server stops
Current Behaviour
Server continues running after the test is over
Steps To Reproduce
Run a test without starting the server beforehand
Check task manager to see that the server is still running after the test is complete
Additional Information
I'm guessing that this was caused by #42 which changed start() to call the bin/server scripts but did not change stop() which still destroys the process started by start().
On *nix systems, terminating the process started as bin/server run is sufficient to signal the server to shut down gracefully.
On Windows, it appears to kill off the cmd.exe process running server.bat but does not kill the child java.exe process which is the actual server
I would try calling server stop instead of trying to kill the process directly.
Azquelt
commented
5 years ago
Issue Overview
On Windows platform, the container does not stop the server
Expected Behaviour
Server stops
Current Behaviour
Server continues running after the test is over
Steps To Reproduce
Additional Information
I'm guessing that this was caused by #42 which changed
start()to call thebin/serverscripts but did not changestop()which still destroys the process started bystart().On *nix systems, terminating the process started as
bin/server runis sufficient to signal the server to shut down gracefully.On Windows, it appears to kill off the
cmd.exeprocess runningserver.batbut does not kill the childjava.exeprocess which is the actual serverI would try calling
server stopinstead of trying to kill the process directly.