Bug 1045628 - Executing RemoteCacheManagerTest generates a "Failed to connect Operation now in progress" exception
Summary: Executing RemoteCacheManagerTest generates a "Failed to connect Operation now...
Keywords:
Status: ASSIGNED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: CPP Client
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Tristan Tarrant
QA Contact: Alan Field
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-20 21:29 UTC by Alan Field
Modified: 2018-01-30 01:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

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 ?


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