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

(7.0.z) IndexOutOfBoundsException when trace logging

    XMLWordPrintable

Details

    • EAP 7.0.9

    Description

      When running with trace logging, I got couple of these STs:

      Exception in thread "OOB-1,test-NodeE-13479" java.lang.IndexOutOfBoundsException: Index: 4, Size: 2
	at java.util.ArrayList.rangeCheck(ArrayList.java:653)
	at java.util.ArrayList.get(ArrayList.java:429)
	at org.jgroups.protocols.pbcast.NAKACK2.handleMessages(NAKACK2.java:868)
	at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:705)
	at org.jgroups.stack.Protocol.up(Protocol.java:425)
	at org.jgroups.protocols.TP.passBatchUp(TP.java:1600)
	at org.jgroups.protocols.TP$BatchHandler.run(TP.java:1820)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

      Seems that part of the list of received messages is removed in handleMessages:864 in

      boolean added=loopback || buf.add(msgs, oob, oob? DUMMY_OOB_MSG : null);

      But the size is not recomputed afterwards.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JGRP-2085 IndexOutOfBoundsException when trace logging

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-10492 [GSS](7.0.z) Upgrade JGroups from 3.6.10 to 3.6.12

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              spyrkob Bartosz Spyrko-Smietanko
              spyrkob Bartosz Spyrko-Smietanko
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: