Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-3391

AMQ224000: Failure in initialisation: java.lang.NullPointerException

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.0.0.ER7
    • 7.0.0.ER5
    • ActiveMQ
    • None
    • Hide

      This is not 100% reproducer, we hit this issue only once:

      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout refactoring_modules
groovy -DEAP_VERSION=7.0.0.ER5 PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=ReplicatedDedicatedFailoverTestWithMdb#testShutdownWithFailback  -DfailIfNoTests=false  -Deap=7x  | tee log
      Show
      This is not 100% reproducer, we hit this issue only once: git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout refactoring_modules groovy -DEAP_VERSION=7.0.0.ER5 PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean test -Dtest=ReplicatedDedicatedFailoverTestWithMdb#testShutdownWithFailback -DfailIfNoTests= false -Deap=7x | tee log

    Description

      We hit NPE during failback in HA scenario with replicated journal in dedicated HA topology which breaks HA.

      Test scenario:
      Start 1st EAP 7 server with Artemis configured as live
      Start 2nd EAP 7 server with Artemis configured as backup
      Send 2000 messages to in InQueue to live
      Start 3rd EAP 7 server with RA configured to connecto to live and deploy MDB which receives messages from InQueue and sends a new message to OutQueue
      When MDB is processing messages then cleanly shutdown live server -> MDB failovers to backup
      After a while start live server again -> MDB failbacks to live
      After MDB processed all messages receive all messages from OutQueue

      Expected result:
      There should 2000 messages received from OutQueue. No duplicated or lost messages. No unfinished XA transactions.

      Actual result:
      During failback Artemis in 1st EAP 7 server did not activated. There NPE in its server log:

      13:01:45,952 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.persistence.impl.journal.JournalStorageManager.loadPreparedTransactions(JournalStorageManager.java:2179) [artemis-server-1.1.0.redhat-7.jar:1.1.0.redhat-7]
        at org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.loadMessageJournal(JournalStorageManager.java:1558) [artemis-server-1.1.0.redhat-7.jar:1.1.0.redhat-7]
        at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:1701) [artemis-server-1.1.0.redhat-7.jar:1.1.0.redhat-7]
        at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:1595) [artemis-server-1.1.0.redhat-7.jar:1.1.0.redhat-7]
        at org.apache.activemq.artemis.core.server.impl.SharedNothingBackupActivation.run(SharedNothingBackupActivation.java:249) [artemis-server-1.1.0.redhat-7.jar:1.1.0.redhat-7]
        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_71]

      Issue is under investigation. This issue was hit only with EAP 7.0.0.ER5. There is no 100% reproducer.

      Attachments

        Issue Links

          is blocked by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-3577 Upgrade Artemis to 1.1.0.wildfly-014

          • 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 related to

          ARTEMIS-422 Loading...

          Activity

            People

              rhn-support-jbertram Justin Bertram
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: