docker-compose stop exits with 137 code and take long time #34
Comments
Hi, I think the issue is that activemq is not pid 1. That should be fixably by replacing
with
You can immediately try it out if you start the container like this:
If you then stop the container with |
Ok, does not help. A wrapping bash script is needed, which traps signals and then explicitly runs |
Instead of using
startamq.sh: |
Nice solution, but that bypasses a whole lot of logic in the |
Using "tini" solves the problem. |
Thanks for the
It stops the container very quickly, however the I have found the problem - the java process is invoked as
The proper invocation should be
I will try to file a bug the upstream ActiveMQ -> https://issues.apache.org/jira/browse/AMQ-8364 |
Hi Petr, Nice catch, although i am not sure exit code 143 is as bad as you think. Besides I have a container in which java is the main process (pid 1) and it also stops with exit code 143 (without tini) I am not pretty sure that i am right, please let me know what you think of it. Regards, |
Thanks you for your contribution. As you probably noticed, I am not using this repo myself anymore for a long time and fail to find the time to maintain it for quite some time now too. Please consider using a fork. This repo is unmaintained and I am going to archive it soon. |
When shutting down activemq docker container using
docker-compose stop
the docker-compose waits for a few seconds and then finally kills the container.The activemq should listen to shutdown signal and gracefully shutdown itself.
I do not know if this is problem with this docker image or the ActiveMQ does not support it at all.
Eg. the mongo container supports this exiting much more quickly and with exit code 0.
Simple docker-compose:
Run it and stop it
The text was updated successfully, but these errors were encountered: