Hi Adel, Thanks for reporting the issue. The qpid.stop script might need more love, though, after sending SIGTERM or SIGKILL event to the broker process, it waits for 1 second and than verifies that process with given PID is still reported by ps (ps -e | grep $1 | wc -l). If process is not reported, no further attempts to send termination signal is made. It seems that in your case the Broker process was present in process table. I could be that it became defunctional. You mentioned that it happens randomly. Do you know what what happens with the broker and broker jvm? Is broker shutdown gracefully? If not, it could be an indication of issue with broker shutdown or jvm exit.
Additionally, I would like to point out that you can call Broker REST API to shutdown the broker (/api/latest/broker/initiateShutdown). As operation name suggests, it does not shutdown broker immediately but rather starts the broker shutdown process and exits. If broker restart is required, a restart operation can be invoked via REST API as well (/api/latest/broker/restart). Kind Regards, Alex On 6 September 2017 at 17:21, Adel Boutros <adelbout...@live.com> wrote: > Hello, > > > In one of our tests, we were having a random failure. It seems we cannot > stop a broker correctly. > > We have a started broker and we call "bin/qpid.stop $BROKER_PID" to stop > it. It seems to work from the first time but maybe not fast enough because > the script keeps trying to kill the broker which is actually dead. > > > Is this a know issue? Is it fixed on a newer version? > > > Command output > > =============== > > Waiting 1 second for 514 to exit > broker/bin/qpid.stop: line 49: kill: (514) - No such process > Waiting 1 second for 514 to exit > broker/bin/qpid.stop: line 41: kill: (514) - No such process > Waiting 1 second for 514 to exit > broker/bin/qpid.stop: line 41: kill: (514) - No such process > Waiting 1 second for 514 to exit > Stopped trying to kill process: 514 > Attempted to stop 2 times > >
