It may be my CLI is behind, but twice now box has ...
# box-products
r
It may be my CLI is behind, but twice now box has failed to stop a server. I tell it to stop and forget, and the CLI says, "Did you leave the server running?" Well no, I'm literally telling it to stop.
b
If you're trying to do it in one command
Copy code
server stop --forget
that sometimes doesn't work if the JVM takes its sweet time shutting down (which happens in the background) and if the PID file is still hanging out out on disk, the forget logic will holler at you.
We used to base whether the servers were running on whether the ports were still bound in the OS and the ports are one of the first to be un-bound when stopping. Now that we use a PID file that's cleaned up on JVM exit, it's more correct, but means servers taking their sweet, sweet time to run JVM shutdown hooks can still be running for a few seconds after the stop command think it's done.
One thing we could do is poll the PID file until it's gone so the stop command blocks until the stop is complete.
r
i ended up ust running it again later and it killed it. also updated my CLI