DevForce Community Forum : Possible EntityManager Threading bug?

Possible EntityManager Threading bug? : You shouldn't see a problem...

Wed, 03 Nov 2010 08:45:00 -700

Author: kimj
Subject: 2281
Posted: 03-Nov-2010 at 8:45am

You shouldn't see a problem with the above in a Silverlight application (or even WPF or WinForms if you want to do async there), but in free threading environments which don't synchronize a callback to the same thread you will see the issue. These environments would include a console application, unit test environments, and ASP.NET. If you do want to do async in these environments then setting the AuthorizedThreadId is required in order to avoid the exception. If you are running in a synchronized threading environment and seeing the error, it does mean that the EntityManager, which is not thread-safe, is being used on multiple threads.

Possible EntityManager Threading bug? : HiI perform an async query...

Wed, 03 Nov 2010 07:18:29 -700

Author: tersiusk
Subject: 2281
Posted: 03-Nov-2010 at 7:18am

Hi

I perform an async query but the entity manager throws an exception because the thread id's don't match. By setting the AuthorizedThreadId to null the exceptions stop. I'm just wondering should AuthorizedThreadId be set to null in these cases or is something else going on?

EntityManager entityManager = new EntityManager();
entityManager.AuthorizedThreadId = null;

var userQuery = entityManager.GetQuery().Where(u => u.Username.ToLower() == valuetoverify.ToString());

userQuery.ExecuteAsync((u) =>
{
    var results = u.Results;
});

Edited by tersiusk - 03-Nov-2010 at 7:19am