This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 855376 - org.infinispan.client.hotrod.PingOnStartupTest.testTopologyFetched randomly fails
org.infinispan.client.hotrod.PingOnStartupTest.testTopologyFetched randomly f...
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: DR2
: 6.2.0
Assigned To: Tristan Tarrant
Martin Gencur
Depends On:
  Show dependency treegraph
Reported: 2012-09-07 10:31 EDT by Anna Manukyan
Modified: 2013-10-06 20:22 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker ISPN-2509 Major Resolved org.infinispan.client.hotrod.PingOnStartupTest.testTopologyFetched randomly fails 2013-12-09 16:58:01 EST

  None (edit)
Comment 1 Anna Manukyan 2012-09-12 08:48:36 EDT
The bug doesn't appear when the test is run separately.
Comment 2 mark yarborough 2012-09-12 09:24:16 EDT
Per ttarrant and mgencur, these are related to tests running in non-representative loading environments and will likely not occur in actual customer deployments. These are not regressions or blockers so will be moved to 6.1. They do not need to be release noted for 6.0.
Comment 3 mark yarborough 2012-11-14 09:42:08 EST
ttarrant will add jira links as appropriate.
Comment 5 Anna Manukyan 2013-01-21 04:49:29 EST
For making sure, that the error message will be later available for investigation, please find the error log here:

Error Message

expected:<2> but was:<1>


java.lang.AssertionError: expected:<2> but was:<1>
	at org.testng.AssertJUnit.failNotEquals(
	at org.testng.AssertJUnit.assertEquals(
	at org.testng.AssertJUnit.assertEquals(
	at org.testng.AssertJUnit.assertEquals(
	at org.infinispan.client.hotrod.PingOnStartupTest$
	at org.infinispan.client.hotrod.test.HotRodClientTestingUtil.withRemoteCacheManager(
	at org.infinispan.client.hotrod.PingOnStartupTest.testTopologyFetched(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.lang.reflect.Method.invoke(
	at org.testng.internal.MethodInvocationHelper.invokeMethod(
	at org.testng.internal.Invoker.invokeMethod(
	at org.testng.internal.Invoker.invokeTestMethod(
	at org.testng.internal.Invoker.invokeTestMethods(
	at org.testng.internal.TestMethodWorker.invokeTestMethods(
	at org.testng.TestRunner.privateRun(
	at org.testng.SuiteRunner.runTest(
	at org.testng.SuiteRunner.access$000(
	at org.testng.SuiteRunner$
	at org.testng.internal.thread.ThreadUtil$
	at java.util.concurrent.FutureTask$Sync.innerRun(
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$
Comment 6 JBoss JIRA Server 2013-03-01 07:24:19 EST
Galder Zamarreño <> made a comment on jira ISPN-2509

I think this might be caused by some DNS issues:

{code}Caused by:
	at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>({code}
Comment 7 JBoss JIRA Server 2013-03-01 07:46:07 EST
Galder Zamarreño <> updated the status of jira ISPN-2509 to Coding In Progress

Note You need to log in before you can comment on or make changes to this bug.