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

backup broker incorrectly becomes live broker despite IOErrors during data replication

XMLWordPrintable

    • Hide

      Still to be defined but it seems the amq-broker-7.2.0/examples/features/ha/replicated-failback-static demo should help to verify the bug.

      Show
      Still to be defined but it seems the amq-broker-7.2.0/examples/features/ha/replicated-failback-static demo should help to verify the bug.

      A backup broker may become a live broker despite getting IOErrors during Data Replication phase when trying replicating paged messages.
      Warning similar to this one appear in the backup broker log file

      2018-07-25 09:38:49,081 WARN  [org.apache.activemq.artemis.core.server] AMQ222086: error handling packet ReplicationPageEventMessage(channel=2, isDelete=true, storeName=test_topic_durable_57, pageNumber=1) for replication: java.io.IOException: Failed to create directory /<mount>/data/paging/26c983-8f-11-90-7cd25fd8

      Despite these warnings the broker becomes the new live broker as per the following logging

      2018-07-25 09:38:49,093 INFO  [org.apache.activemq.artemis.core.server] AMQ221037: ActiveMQServerImpl::serverUUID=1e31b-0a-11-a1d-7a5fd8 to become 'live'

        1. lastStart.log
          472 kB
        2. replicated-failback-static-ENTMQBR-1831.tgz
          8 kB

              rhn-support-jbertram Justin Bertram
              rhn-support-tmielke Torsten Mielke
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: