Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2062

priorityBackup=true with JMS clients fails back but stops receiving messages

    XMLWordPrintable

Details

    • Compatibility/Configuration, User Experience
    • Hide
      • Configure a 3 broker nob as per attached configuration using A-MQ v6.1.1-423
      • Compile and run the FTFReceiver
      • Compile and run the FTFSender
      • while (not reproduced)
        • touch the activemq.xml for broker 2
        • observe failover to broker 3
        • observe fail back to broker 2
        • observe if FTFReceiver continues to receive messages after fail back
      Show
      Configure a 3 broker nob as per attached configuration using A-MQ v6.1.1-423 Compile and run the FTFReceiver Compile and run the FTFSender while (not reproduced) touch the activemq.xml for broker 2 observe failover to broker 3 observe fail back to broker 2 observe if FTFReceiver continues to receive messages after fail back

    Description

      Server process (Producer) was running on Broker 1 and the client process (Consumer) was running on Broker 2.

      While an ACL update was being done , activemq.xml was touched in that process which triggered Soft restart of Broker2 . Client Process switched to Broker 3 and moved back to Broker 2 once it was recovered(since priority back up was set to true) . After that there was no communication between Server and Client . We came out of this situation by recovering the broker processes.

      Note that if priorityBackup=false the behaviour is not seen, and that with priorityBackup=true it is seen infrequently. By infrequently I mean I had to run the attached reproducer and force failovers Broker2 -> Broker3 and then back to Broker2 maybe 20 times before I saw the behaviour.

      Attachments

        Activity

          People

            gtully@redhat.com Gary Tully
            rhn-support-rkieley Roderick Kieley
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: