Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-5733

kill -9 always results in failure signal

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Abandoned
    • 5.11.1
    • None
    • Distribution
    • None

    Description

      Using https://github.com/rgevaert/activemq2deb I am trying to distribute upgrades to our fleet. This results in failure each time.

      Looking into the matter the activemq script tries to stop the broker via JMX. This is not configured, so fails.

      It falls back to issuing "kill -9 <PID>" then immediately exits with code 1. This code 1 causes the packaging script to bail and thus we end up with a mess.

      A possible solution is to return the "kill" command's own result. This doesn't necessarily reflect whether "kill" succeeded in terminating the PID however.

      A second possible solution is to detect the presence of 'start-stop-daemon' and use this in preference. Narrows down the cases in which it does not work at least.

      I am of the opinion that a script aiming of cross-platform compatibility is probably never going to work completely so detecting and making use of per-system tooling is probably best long term, meantime would returning "kill's" exit code help?

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            jmkgreen James Green
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment