Bug 1045628

Summary:	Executing RemoteCacheManagerTest generates a "Failed to connect Operation now in progress" exception
Product:	[JBoss] JBoss Data Grid 6	Reporter:	Alan Field <afield>
Component:	CPP Client	Assignee:	Tristan Tarrant <ttarrant>
Status:	ASSIGNED ---	QA Contact:	Alan Field <afield>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	mgencur, pzapataf, sjacobs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Alan Field 2013-12-20 21:29:07 UTC

Description of problem:
The following three test classes display this issue. (RemoteCacheManagerTest, ClientAsymmetricClusterTest, and ServerRestartTest) 

This is what I see when trying to run RemoteCacheManagerTest:

a) A Hot Rod server is started on port 15233
b) The default constructor for the RemoteCacheManager is called, and a server on the default port (11222) is added to the configuration object
c) TcpTransportFactory::pingServers() fails and throws a HotRodClientException "Failed to connect Operation now in progress"

Side note: Can that error message be changed to something more understandable, like "Ping operation to <server>:<port> failed"?

At first this seems like a test configuration issue, and I have been trying to figure out where the 15233 port is set. Then I tried running the same test using the Java Hot Rod client in the Infinispan project, and it also starts a server on port 15233. In this case the test succeeds, though. Now I am wondering if the implementation of the ping operation is different between the two clients.

Comment 2 Alan Field 2013-12-23 16:57:10 UTC

This issue is related to host name resolution under IPv6. Setting the "HOTROD_IPSTACK=IPV4" environment variable is a workaround until this is fixed. This error can still occur even if this environment variable is set.

Comment 3 Tristan Tarrant 2014-12-03 14:14:34 UTC

Alan does this still fail ?