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

[LTS] Shared Store: allow-failback=true throws NullPointerException at failover

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • AMQ 7.9.0.GA
    • disaster-recovery
    • None
    • False
    • None
    • False
    • Hide

      Disable failback fix seems to fix the issue.

      <allow-failback>false</allow-failback> 
      Show
      Disable failback fix seems to fix the issue. <allow-failback> false </allow-failback>
    • Hide

      Just two brokers with all defaults and shared store, then kill the master.

      Show
      Just two brokers with all defaults and shared store, then kill the master.

      With a default share-store setup, when the backup take over a NPE is trow.

      INFO  [org.apache.activemq.artemis.core.server] AMQ221010: Backup Server is now live
      ERROR [org.apache.activemq.artemis.core.server] AMQ224000: Failure in initialisation: java.lang.NullPointerException
          at org.apache.activemq.artemis.core.server.impl.SharedStoreBackupActivation$FailbackChecker.<init>(SharedStoreBackupActivation.java:256) [artemis-server-2.18.0.redhat-00010.jar:2.18.0.redhat-00010]
          at org.apache.activemq.artemis.core.server.impl.SharedStoreBackupActivation.startFailbackChecker(SharedStoreBackupActivation.java:248) [artemis-server-2.18.0.redhat-00010.jar:2.18.0.redhat-00010]
          at org.apache.activemq.artemis.core.server.impl.SharedStoreBackupActivation.run(SharedStoreBackupActivation.java:138) [artemis-server-2.18.0.redhat-00010.jar:2.18.0.redhat-00010]
          at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$ActivationThread.run(ActiveMQServerImpl.java:4271) [artemis-server-2.18.0.redhat-00010.jar:2.18.0.redhat-00010]
       

              rhn-support-jbertram Justin Bertram
              rhn-support-agagliar Antonio Gagliardi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: