Bug 1044032

Summary: Access violation exception occurs when closing socket on Windows
Product: [JBoss] JBoss Data Grid 6 Reporter: Alan Field <afield>
Component: CPP ClientAssignee: Ion Savin <isavin>
Status: CLOSED WORKSFORME QA Contact: Alan Field <afield>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: afield, dmehra, mgencur, pzapataf, sjacobs, ttarrant
Target Milestone: GA   
Target Release: 6.4.0   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-26 12:27:42 UTC 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
Test log
none
JVM crash log none

Description Alan Field 2013-12-17 16:32:32 UTC
Created attachment 837782 [details]
Test log

Running the org.infinispan.client.hotrod.HotRodServerStartStopTest.testTouchServer method from JniTest triggers the following JVM crash:

8: #
8: # A fatal error has been detected by the Java Runtime Environment:
8: #
8: #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d7356f9, pid=428, tid=4004
8: #
8: # JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
8: # Java VM: Java HotSpot(TM) Client VM (24.45-b08 mixed mode windows-x86 )
8: # Problematic frame:
8: # C  [hotrod.dll+0x856f9]  infinispan::hotrod::transport::Socket::close+0x19
8: #
8: # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
8: #
8: # An error report file with more information is saved as:
8: # C:\Users\afield\Documents\GitHub\cpp-client\build\hs_err_pid428.log

I have attached a log with the output of the JniTest execution, and I'll also attach the specified hs_err_pid file. This is happening on both 32 and 64 bit Windows platforms.

Comment 1 Alan Field 2013-12-17 16:33:13 UTC
Created attachment 837783 [details]
JVM crash log

Comment 4 Tristan Tarrant 2014-12-03 14:12:52 UTC
Alan can you plese verify if this happens with 6.3/6.4

Comment 5 Ion Savin 2015-04-29 14:57:44 UTC
Cannot reproduce this on jdg-6.4.x/jdg-6.5.x on Windows x86/x64. Alan, can you please verify that this is no longer an issue for you either? Thanks!

Comment 6 Alan Field 2015-05-26 12:27:42 UTC
Not seeing this any more with JDG 6.5 builds.