Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-4194

[LTS] Server start exception before activation can cause a zombie broker

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Done
    • AMQ 7.4.5.CR4
    • None
    • None
    • None

    Description

      Run::execute:

      1. start a broker
      2. add several external components while starting them right after

      If the broker is getting started and, right before activating, throw an exception (eg on NodeManager::start), its process won't be stopped because the ActivationFailureListener won't get triggered.

      if the broker is getting started and, right before activating it, it throws an exception AND raise an I/O critical error (eg JdbcNodeManager:.start), a separate Thread would race to stop the broker external components while they are being added (and started): if some of these components are added AFTER the stop has completed or are started after being stopped, they would prevent the process to stop.

      Attachments

        Issue Links

          Activity

            People

              fnigro Francesco Nigro
              fnigro Francesco Nigro
              Tiago Bueno Tiago Bueno
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: