Bug 1045623 - Executing JniTest causes a number of "Pool is closed" exceptions
Summary: Executing JniTest causes a number of "Pool is closed" exceptions
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:18 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)
"Pool is closed" test log (102.59 KB, text/x-log)
2013-12-20 21:18 UTC, Alan Field 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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 ?
Note You need to log in before you can comment on or make changes to this bug.