Bug 1051683

Summary: ConnectionPool::invalidateObject does not remove object from queues
Product: [JBoss] JBoss Data Grid 6 Reporter: Alan Field <afield>
Component: CPP ClientAssignee: Tristan Tarrant <ttarrant>
Status: VERIFIED --- QA Contact: Alan Field <afield>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: mgencur
Target Milestone: CR2   
Target Release: 6.2.1   
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:
Embargoed:
Attachments:
Description Flags
Windows 7 32-bit test log
none
Windows 7 32-bit JVM crash log
none
Windows 7 64-bit test log
none
Windows 7 64-bit JVM crash log none

Description Alan Field 2014-01-10 21:10:45 UTC 
Description of problem:

The C++ libraries provided with the JDG 6.2.0 CR2 build are not able to successfully run the JNI tests on Windows 7 without JVM crashes. On 32-bit Windows, the tests are all executed successfully, but the JVM crashes. On 64-bit Windows, many of the tests fail with the "Pool is closed" exceptions and the JVM crashes. test and JVM crash logs will be attached.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Alan Field 2014-01-10 21:12:13 UTC 
Created attachment 848395 [details]
Windows 7 32-bit test log
Comment 2 Alan Field 2014-01-10 21:12:43 UTC 
Created attachment 848396 [details]
Windows 7 32-bit JVM crash log
Comment 3 Alan Field 2014-01-10 21:13:07 UTC 
Created attachment 848397 [details]
Windows 7 64-bit test log
Comment 4 Alan Field 2014-01-10 21:13:42 UTC 
Created attachment 848399 [details]
Windows 7 64-bit JVM crash log
Comment 6 Alan Field 2014-01-11 22:17:25 UTC 
The errors on the 64-bit build go away when the HOTROD_IPSTACK environment variable is set to "IPV4". The crash on the 32-bit build still occurs.
Comment 7 Radim Vansa 2014-01-13 10:53:28 UTC 
Alan, could you provide also core dumps for the failed tests? This article might help: http://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx
Also, building with debug options and trying to reproduce that might help as we don't have PDB files yet.
Comment 8 Radim Vansa 2014-01-13 16:32:20 UTC 
The root cause for the crash was found - incorrect error handling for request throwing transport exception. See JIRA for details.
Comment 11 Alan Field 2014-03-28 18:55:52 UTC 
Verified with JDG 6.2.1 CR2