通缉:不受 AbandonedMutexException 影响的跨进程同步

Wanted: Cross-process synch that doesn#39;t suffer from AbandonedMutexException(通缉:不受 AbandonedMutexException 影响的跨进程同步)

本文介绍了通缉:不受 AbandonedMutexException 影响的跨进程同步的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

I have several threads that acquire Mutexes and then terminate.

The mutexes are stored in a main repository, and are properly released when the program exists. However, when the thread that allocated a Mutex exists, the mutex gets released automatically, and subsequent acquire AbandonedMutexException (also according to the documentation).

How can I avoid this exception, and keep using a Mutex even after the allocating thread finished? Is there another, more appropriate synchronization construct in .Net that doesn't have this limitation.

Note - I am looking for a cross-process synch mechanism with similar semantics to Mutex.

解决方案

Looks like EventWaitHandle does what I want. It has a constructor that takes a name, so it's perfect for cross-process synch, and it doesn't have this problem.

这篇关于通缉:不受 AbandonedMutexException 影响的跨进程同步的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

本文标题为:通缉:不受 AbandonedMutexException 影响的跨进程同步