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;


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


Post a Comment

Popular posts from this blog

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 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.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.