Bug 1021815

Summary:	JGroups: Intermittent failures in LargeStateTransferTest
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Richard Janík <rjanik>
Component:	Clustering	Assignee:	Richard Achmatowicz <rachmato>
Status:	CLOSED NOTABUG	QA Contact:	Jitka Kozana <jkudrnac>
Severity:	low	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.2.0	CC:	rachmato
Target Milestone:	---
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	JGroups testsuite
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-27 14:35:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Richard Janík 2013-10-22 07:18:31 UTC

Description of problem:

EAP 6.2.0.ER6
JGroups 3.2.12.Final

Note: I have seen this in some previous versions as well and was looking into it:

UDP variants of org.jgroups.tests.LargeStateTransferTest.testStateTransferX often fail with:

Error Message

requester view is [requester|0] [requester], but should have 2 members

Stacktrace


java.lang.AssertionError 
at org.jgroups.tests.LargeStateTransferTest._testStateTransfer(LargeStateTransferTest.java:82) 
at org.jgroups.tests.LargeStateTransferTest.testStateTransfer1(LargeStateTransferTest.java:57) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
at java.lang.reflect.Method.invoke(Method.java:597) 
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) 
at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:46) 
at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37) 
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) 
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 
at java.util.concurrent.FutureTask.run(FutureTask.java:138) 
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) 
at java.lang.Thread.run(Thread.java:662) 

The issue is not in JGroups, but rather in the testsuite and it has already been fixed in upstream so component upgrades will solve this in time.

Comment 1 Richard Achmatowicz 2014-03-27 14:33:13 UTC

NOTE: A number of EAP clustering issues relate to failures in the JGroups testsuite. Some of these failures relate to tests of features of JGroups which are not used by EAP.

As of EAP 6.3, a modified version of the JGroups testsuite (JGroups version 3.2.13) is being executed which excludes tests of JGroups features which are not used by EAP. Only the testsuite has been modified/fixed; the product is unchanged. The list of features can be found here: https://mojo.redhat.com/docs/DOC-938761

EAP 6.3 Clustering issues relating to failures in the JGroups testsuite are being closed if they relate to features not used by EAP.