Skip to main content

Azure Service Fabric: State of an Actor is not persisted | Actor ID

We have in our Azure Service Fabric cluster an actor called SmsActorService that haves a method that allow us to get the next SMS.
The actor works great, when we want to send an SMS to our actor works great, but when we want to get a SMS, surprise, we have null reference exception when we want to access the actor state.

Send SMS to actor
 IAct0r mobileDevice = ActorProxy.Create<IAct0r>(
                        new ActorId(smsToSent.Value.PhoneNumber),
                        new Uri("fabric:/ITCamp.SF/Act0rActorService"));

                    await mobileDevice.ReceiveSmsAsync(smsToSent.Value);

Get SMS from actor
int id = 1000;
IAct0r mobileDevice = ActorProxy.Create<IAct0r>(
                new ActorId(id),
                new Uri("fabric:/ITCamp.SF/Act0rActorService"));
Sms sms = mobileDevice.GetNextSms().Result;

Even if we know that we already created the actor with the given ID and we have our state saved, when we access it, surprise, the state is not set. It's like we just created our actor for the first time.

After a few minutes of debugging, we identify the problem. When we send the SMS to our actor, we specify the Actor ID as a string (PhoneNumber). When we want to access the actor in the second call, we specify the Actor ID as int.
This is enough for Azure Service Fabric to create two different instances of actors. One that has ID 1000 (long) and another one that has ID '1000' (as string).

The problem can be solved easily by converting both ID to the same time. I recommend to use only string because is more safe for long time and you will never ask yourself if others used long, string or GUID.
int id = 1000;
IAct0r mobileDevice = ActorProxy.Create<IAct0r>(
                new ActorId(id.ToString()),
                new Uri("fabric:/ITCamp.SF/Act0rActorService"));
Sms sms = mobileDevice.GetNextSms().Result;

Comments

  1. Ahhh ! Been struggling with this for an hour, thanks !!!

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...