Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5453

NPE during backup activation in collocated HA topology

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 10.0.0.CR5
    • 10.0.0.CR2
    • JMS
    • None
    • Workaround Exists
    • Hide

      add an explicit slave configuration

                      <replication-colocated backup-port-offset="50" request-backup="true">
                    <slave/>
                </replication-colocated>
      Show
      add an explicit slave configuration <replication-colocated backup-port-offset="50" request-backup="true"> <slave/> </replication-colocated>

    Description

      If there are 2 EAP 7.0.0.DR11(Artemis 1.1.0) in collocated HA topology with replicated journal then backup does not activate after one server is killed. There is NPE in log of 2nd EAP server:

      10:13:12,231 ERROR [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ224000: Failure in initialisation: java.lang.NullPointerException
	at org.apache.activemq.artemis.core.server.impl.SharedNothingBackupActivation.run(SharedNothingBackupActivation.java:235)
	at java.lang.Thread.run(Thread.java:745)

10:13:12,235 ERROR [stderr] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) java.lang.NullPointerException
10:13:12,235 ERROR [stderr] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) 	at org.apache.activemq.artemis.core.server.impl.SharedNothingBackupActivation.run(SharedNothingBackupActivation.java:235)
10:13:12,236 ERROR [stderr] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) 	at java.lang.Thread.run(Thread.java:745)

      Attaching configuration of both of the servers.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-1208 NPE during backup activation in collocated HA topology

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is caused by

          ARTEMIS-243 Loading...

          Activity

            People

              csuconic@redhat.com Clebert Suconic
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: