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

Activation failure can result in zombie broker

    XMLWordPrintable

Details

    • Medium
    • Hide
      In prior releases, if a live-backup broker group was configured to use shared store high availability, the live broker might fail to properly activate after a restart, but would continue to hold the journal lock. For example, this issue might occur if the live-backup group was using a network file system (NFS), and the NFS was unexpectedly stopped or removed, causing the live broker to restart. This situation resulted in a a non-functional broker that couldn't service clients but which prevented the backup broker from activating. This issue is now resolved.
      Show
      In prior releases, if a live-backup broker group was configured to use shared store high availability, the live broker might fail to properly activate after a restart, but would continue to hold the journal lock. For example, this issue might occur if the live-backup group was using a network file system (NFS), and the NFS was unexpectedly stopped or removed, causing the live broker to restart. This situation resulted in a a non-functional broker that couldn't service clients but which prevented the backup broker from activating. This issue is now resolved.
    • Documented as Resolved Issue
    • ?
    • Verified in a release

    Description

      A pair of master/slave brokers configured to use shared NFS store become <defunct> when the NFS shared store is removed i.e. NFS service is stoped on the machine serving the file system.

      The master broker restarts after the NFS failure in a state where it holds the lock but does not start/deploy the JMS objects and neither does it allow slave broker to get the lock

      Attachments

        Issue Links

          Activity

            People

              rhn-support-jbertram Justin Bertram
              rhn-support-hnaram Herambh Naram
              Tiago Bueno Tiago Bueno
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: