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

ActiveMQ standalone script doesn't return with 0 when stop is called.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 5.4.1
    • 5.4.2
    • None
    • None
    • Patch Available

    Description

      I was testing to see if the ./bin/activemq script was LSB compatible (I want to integrate activemq into a pacemaker setup).

      When calling ./bin/activemq stop, the script should return 0 on success.

      The problem is in the invokeJar function. In the 'stop' case , the value of RET is set in the context of a forked process.
      The proposed fix, is identical to how RET is handled in the other 2 cases.

      Attachments

        1. activemq-return-value.patch
          0.7 kB
          Alexander Fisher

        Activity

          People

            dejanb Dejan Bosanac
            alexjfisher Alexander Fisher
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: