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

OOM caused by jgroups objects UNICAST3$SenderEntry#1

    Details

    • Steps to Reproduce:
      Hide

      You can run the test using the following steps.

      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
      cd eap-tests-hornetq/scripts/
      groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/217//artifact/jboss-eap.zip 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=JGroupsClusterTestCase#clusterTestWithKillOfServerInCluster  -DfailIfNoTests=false -Deap=7x -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1520950239-SNAPSHOT | tee log
      

      Show
      You can run the test using the following steps. git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/217//artifact/jboss-eap.zip 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=JGroupsClusterTestCase#clusterTestWithKillOfServerInCluster -DfailIfNoTests=false -Deap=7x -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1520950239-SNAPSHOT | tee log

      Description

      JGroups objects UNICAST3$SenderEntry#1 caused OOM on Wildfly server during the boot. See attached picture.

      User impact: If users use JGroups for clustering, the server may get OOM what can cause undefined behavior.

      The blocker priority was set, because this is regression against previous versions of Wildfly and the OOM is serious error which prevents server to work properly.

      The issue was hit in following scenario.

      1. start two servers (nodes) in cluster with one queue
      2. producer starts to send messages to queue to node-1
      3. node-2 is killed and restarted during sending messages <---- Here the test failed, when the node-2 was started after that it had been killed.
      4. start consumer on node-2 which reads messages from queue
      5. servers are stopped

      The Wildfly was built from following source code:
      repo: https://github.com/jmesnil/wildfly
      branch: WFLY-9407_upgrade_artemis_2.5.0
      commit SHA: 06c878a313d3cad323889d017e60fd5533204d1a
      JGroups version: 4.0.10.Final

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                pferraro Paul Ferraro
                Reporter:
                eduda Erich Duda
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: