Why Mutex doesn't guarantee unique instance randomly?

Asked Sep 16 '15 at 14:46

Active Sep 16 '15 at 14:46

Viewed 81 times

I use mutex to make sure that only one instance of my program is running on a server.

Mutex mutex = new Mutex(false, Common.MutexName);


        if (!mutex.WaitOne(1000, false))
        {
            Console.WriteLine("Another process is already working.");
            return;
        }

It works in most cases, but randomly I do see multiple instances of same application were running. Am I missing anything? The server is a windows 2008.

asked Sep 16 '15 at 14:46

daxu

3,514
5
38
76

3

were they running under the same user/session? – Daniel A. White Sep 16 '15 at 14:50
relevant: http://stackoverflow.com/questions/4223061/how-to-implement-single-instance-per-machine-application – Daniel A. White Sep 16 '15 at 14:50
@DanielA.White IIRC named mutex are cross-process enabled. Are they limited to session/user ? – Royi Namir Sep 16 '15 at 14:53
Hi Daniel, I think I copied this code from Internet long time ago, and it does work in most cases. I will try your link – daxu Sep 16 '15 at 14:54
by default its per session/user. – Daniel A. White Sep 16 '15 at 14:54
@daxu Try prefix the name with `Global\`. [read here](https://msdn.microsoft.com/en-us/library/system.threading.mutex(v=vs.110).aspx) – Royi Namir Sep 16 '15 at 15:01
Definitely read this community wiki answer: http://stackoverflow.com/a/229567/106159 – Matthew Watson Sep 16 '15 at 15:24

Why Mutex doesn't guarantee unique instance randomly?

0 Answers0