Bug 1045623

Summary: Executing JniTest causes a number of "Pool is closed" exceptions
Product: [JBoss] JBoss Data Grid 6 Reporter: Alan Field <afield>
Component: CPP ClientAssignee: Tristan Tarrant <ttarrant>
Status: ASSIGNED --- QA Contact: Alan Field <afield>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: 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:
Attachments:
Description Flags
"Pool is closed" test log none

Description Alan Field 2013-12-20 21:18:45 UTC
Created attachment 839816 [details]
"Pool is closed" test log

Description of problem:

After applying the following two commits:

HRCPP-106 C++ exceptions are not propagated through JNI layer
ee698db8a5 
isavin authored 4 days ago
 tristantarrant committed 2 days ago

HRCPP-103 ConnectionPool::borrowObject throws HotRodClientException w… …
ef0e9c3b3c 
isavin authored 4 days ago
 tristantarrant committed 3 days ago

The tests in JniTest are throwing many "Pool is closed" exceptions on RHEL and Windows. Not sure if this is related to the JNI/SWIG layer or in the C++ client, but it prevents tests from running successfully. Attaching a log with the stack traces.

Comment 2 Alan Field 2013-12-23 16:56:20 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.

Comment 3 Tristan Tarrant 2014-12-03 14:13:52 UTC
Alan does this still fail ?