Skip to main content

Azure Service Fabric: The primary or stateless instance for the partition has invalid address, this means that right address from the replica/instance is not registered in the system.

What should you do when you are using Azure Service Fabric and you receive the following error code when you call a Reliable Service that is Stateful:
The primary or stateless instance for the partition has invalid address, this means that right address from the replica/instance is not registered in the system.
Sample
Remote Call:
IStatefull smsService = ServiceProxy.Create<IStatefull>(
                        new Uri("fabric:/ITCamp.SF/Stateful"),new ServicePartitionKey(1));
                   
await smsService.SendSmsAsync(
    phoneNumber,
    $"{DateTime.Now.ToShortTimeString()} Hello ITCamp!, from '{phoneNumber}'");                    

Service
    internal sealed class Stateful : StatefulService, IStatefull
    {
        public Stateful(StatefulServiceContext context)
            : base(context)
        { }

        protected override IEnumerable<ServiceReplicaListener> CreateServiceReplicaListeners()
        {
            return new ServiceReplicaListener[0];
        }

        protected override async Task RunAsync(CancellationToken cancellationToken)
        {
            IReliableQueue<Sms> smsToSetQueue = await StateManager.GetOrAddAsync<IReliableQueue<Sms>>("smsToSent");

            while (true)
            {
                cancellationToken.ThrowIfCancellationRequested();
                await Task.Delay(TimeSpan.FromSeconds(1), cancellationToken);

                using (ITransaction tx=StateManager.CreateTransaction())
                {
                    ConditionalValue<Sms> smsToSent = await smsToSetQueue.TryDequeueAsync(tx);

                    if (!smsToSent.HasValue)
                    {
                        await tx.CommitAsync();
                        continue;        
                    }

                    ServiceEventSource.Current.ServiceMessage(this, 
                        "SMS to the phone number '{0}' was send to end client",
                        smsToSent.Value.PhoneNumber);
                    await tx.CommitAsync();
                }                               
            }
        }

        public async Task SendSmsAsync(string phoneNumber, string message)
        {
            IReliableQueue<Sms> smsToSetQueue = await StateManager.GetOrAddAsync<IReliableQueue<Sms>>("smsToSent");

            using (ITransaction tx = StateManager.CreateTransaction())
            {
                await smsToSetQueue.EnqueueAsync(tx, new Sms()
                {
                    Message = message,
                    PhoneNumber = phoneNumber
                });
                await tx.CommitAsync();
            }
        }
    }

Solution
The problem is from CreateServiceReplicaListeners and is happening because there is no listener set. The only thing that you need to do to be able to make a call over Service Remoting is to set the listener as below.

    internal sealed class Stateful : StatefulService, IStatefull
    {
        public Stateful(StatefulServiceContext context)
            : base(context)
        { }

        protected override IEnumerable<ServiceReplicaListener> CreateServiceReplicaListeners()
        {
            return new[] { new ServiceReplicaListener(context => this.CreateServiceRemotingListener(context)) };
        }

    ....
    }

Comments

  1. This is out of date. Do you have an example of the next version of the DLLs where there is no method CreateServiceRemotingListener() ??

    ReplyDelete
  2. Awesome catch! thanks! note: same trick for stateless too, only that it's ServiceInstanceListener instead of ServiceReplicaListener

    ReplyDelete
  3. I really like the way you put the information. Also thanks to JDer to mention the important point for stateless service. Great guidance post and can save lot of time.

    ReplyDelete
  4. For stateless, this does not compile:
    protected override IEnumerable CreateServiceInstanceListeners()
    {
    return new[] { new ServiceReplicaListener(context => this.ServiceInstanceListener(context)) };

    //return new ServiceInstanceListener[0];
    }

    ReplyDelete
    Replies
    1. Yes, the code doen't compiles anymore, because at the Build a new version of SDK wa released, that is not backward compatible with RC.

      Delete
  5. If anyone have issues with CreateServiceRemotingListener not being found, it is an extension method and you can get it by adding the following using in your service:

    using Microsoft.ServiceFabric.Services.Remoting.Runtime;

    ReplyDelete
    Replies
    1. Any resolution to this? I can find it either.

      Delete
  6. Thanks for all the input from you guys and great writeup as well.
    For stateless, this works for me:
    protected override IEnumerable CreateServiceInstanceListeners()
    {
    return new[] { new ServiceInstanceListener(context => this.CreateServiceRemotingListener(context)) };

    }

    ReplyDelete
    Replies
    1. Thanks Michael! After hours of frustration, this was exactly what I needed!

      Delete

Post a Comment

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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

[Post-Event] Codecamp Conference Cluj-Napoca - Nov 19, 2016

Last day I was invited to another Codecamp Conference, that took place in Cluj-Napoca. Like other Codecamp Conferences, the event was very big, with more than 1.000 participants and 70 sessions. There were 10 tracks in parallel, so it was pretty hard to decide at  what session you want to join.
It was great to join this conference and I hope that you discovered something new during the conference.
At this event I talked about Azure IoT Hub and how we can use it to connect devices from the field. I had a lot of demos using Raspberry PI 3 and Simplelink SensorTag. Most of the samples were written in C++ and Node.JS and people were impressed that even if we are using Microsoft technologies, we are not limited to C# and .NET. World and Microsoft are changing so fast. Just looking and Azure IoT Hub and new features that were launched and I'm pressed (Jobs, Methods, Device Twin).
On backend my demos covered Stream Analytics, Event Hub, Azure Object Storage and DocumentDB.

Title:
What abo…