Bug ID: JDK-8046024 JDI shared memory transport failed with "Observed abandoned IP mutex"

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

JDK 7	JDK 8	JDK 9
7u76Fixed	8u20Fixed	9 b22Fixed

TESTFAIL:com/sun/jdi/RedefineCrossEvent.java
com/sun/jdi/RedefineCrossEvent.java

This test failed in jdk9-dev nightly on one windows:

Testing StackOverflowCaughtTarg with java.lang.NullPointerException/caught=false/uncaught=false suspend=Thread
JVM version:1.9.0-ea
JDI version: 1.8
JVM description: Java Debug Interface (Reference Implementation) version 1.8 
Java Debug Wire Protocol (Reference Implementation) version 1.8
JVM Debug Interface version 1.2
JVM version 1.9.0-ea (Java HotSpot(TM) Client VM, mixed mode, sharing)
FATAL ERROR in native method: Shared Memory Transport "shmem_md.c" (Jun  4 2014), line 212: Observed abandoned IP mutex. Aborting.

	at com.sun.tools.jdi.SharedMemoryConnection.close0(Native Method)
	at com.sun.tools.jdi.SharedMemoryConnection.close(SharedMemoryConnection.java:70)
	- locked <0x041036d8> (a java.lang.Object)
	at com.sun.tools.jdi.TargetVM.run(TargetVM.java:130)
	at java.lang.Thread.run(Thread.java:745)

RULE nsk/jdi/BScenarios/singlethrd/tc01x002 ExitCode 1 RULE nsk/jdi/ClassLoaderReference/definedClasses/definedclasses002 ExitCode 1 RULE nsk/jdi/ClassType/superclass/superclass002 ExitCode 1 RULE nsk/jdi/ObjectReference/setValue/setvalue002 ExitCode 1 RULE nsk/jdi/ReferenceType/visibleFields/visibfield005 ExitCode 1 RULE nsk/jdi/Value/type/type003 ExitCode 1
11-07-2014
RULE com/sun/jdi/DeleteEventRequestsTest.java ExitCode 1 RULE com/sun/jdi/FieldWatchpoints.java ExitCode 1 RULE nsk/jdi/Field/isEnumConstant/isenumconstant001 ExitCode 1 RULE nsk/jdi/ThreadGroupReference/toString/tostring001 ExitCode 1 RULE nsk/jdi/TypeComponent/declaringType/decltype009 ExitCode 1
11-07-2014
RULE nsk/jdb/fields/fields001 ExitCode 97 RULE nsk/jdb/reenter/reenter001 ExitCode 97 RULE nsk/jdb/watch/watch002 ExitCode 97
01-07-2014
This failure mode was observed in an Aurora Adhoc job: nsk/jdi/BScenarios/multithrd/tc01x001 nsk/jdi/BScenarios/singlethrd/tc03x001 nsk/jdi/ObjectReference/entryCount/entrycount002 nsk/jdi/StepRequest/addInstanceFilter/instancefilter004 nsk/jdi/TypeComponent/isStatic/isstatic004 nsk/jdi/VirtualMachine/redefineClasses/redefineclasses012 nsk/jdi/VirtualMachine/redefineClasses/redefineclasses029 nsk/jdi/WatchpointRequest/addClassFilter_s/filter_s004 These tests failed due to: FATAL ERROR in native method: Shared Memory Transport "shmem_md.c" (Jun 12 2014), line 212: Observed abandoned IP mutex. Aborting.
20-06-2014
The fix for JDK-8032901 has been backed out.
19-06-2014
When the fix for JDK-8032901 was discussed this was considered a rare case and a fatal error as it meant a thread had terminated unexpectedly and as a result the state of things was completely unknown. Do these tests deliberately abandon the mutex? That aside these tests should have been run prior to that fix being pushed.
18-06-2014
If we are not able to make progress on this soon, I suggest we revert the fix for JDK-8032901.
12-06-2014
This is a consequence of the fix for JDK-8032901.
09-06-2014

Duplicate :	JDK-8046303 - com/sun/jdi/ExceptionEvents.java fails with "Observed abandoned IP mutex"
Relates :	JDK-8047334 - Reapply fix for "8032901 WaitForMultipleObjects() return value not handled appropriately"
Relates :	JDK-8032901 - WaitForMultipleObjects() return value not handled appropriately