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

Message NODE_X::MESSAGE_Y not found in retransmission table in REPL stress tests

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Critical
    • None
    • 7.1.0.DR13
    • Clustering
    • None

    Description

      This WARN message was seen in stress test scenarios stress-session-repl-sync and stress-session-repl-async in server logs:

      07:14:56,291 WARN  [org.jboss.as.clustering.jgroups.protocol.NAKACK2] (thread-2) JGRP000041: perf18: message perf19::367290 not found in retransmission table
      

      Message occurs during the test on all the nodes (more than 150 000 occurences on each node) always after cluster-wide rebalance finished:

      07:11:39,119 INFO  [org.infinispan.CLUSTER] (remote-thread--p5-t5) ISPN000336: Finished cluster-wide rebalance for cache clusterbench-ee7.ear.clusterbench-ee7-web-passivating.war, topology id = 6
      

      It seems the message occurs more frequently at the end of the test.

      This error started occuring in DR12 builds and is probably causing performance drops and sampling errors in a repl-async scenario.
      Check the performance report for repl-async scenario:
      http://download.eng.brq.redhat.com/scratch/mvinkler/reports/2017-03-09_11-48-54/stress.html

      Link to server logs:
      repl-sync scenario
      http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-stress-session-repl-sync/14/console-perf18/

      repl-async scenario
      http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-stress-session-repl-async/7/console-perf18/

      The message is the same as in failover test scenario ejb-ejbservlet-jvmkill-repl-async (JBEAP-9000).

      Attachments

        Issue Links

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              dcihak@redhat.com Daniel Cihak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: