Skip to main content

Unity: Interception Call Handler called multiple times

For a project we are using Unity 2.0 interception with policy injection to create and manage our NHibernate session. Therefore we created a custom ICallHandler in combination with a HandlerAttribute.
[AttributeUsage(AttributeTargets.Method)]
    public class NHibernateUnitOfWorkHandlerAttribute : HandlerAttribute
    {
        private bool _createTransaction;

        public NHibernateUnitOfWorkHandlerAttribute(bool createTransaction=false)
        {
            _createTransaction = createTransaction;
        }

        public override ICallHandler CreateHandler(IUnityContainer container)
        {
            return new NHibernateUnitOfWorkHandler(Order,_createTransaction);
        }
    }


    public class NHibernateUnitOfWorkHandler : ICallHandler
    {
        public NHibernateUnitOfWorkHandler(int order,bool createTransaction)
        {
            this.Order = order;
            this.CreateTransaction = createTransaction;
        }

        public IMethodReturn Invoke(IMethodInvocation input, GetNextHandlerDelegate getNext)
        {
            IMethodReturn result=null;

            try
            {
                using (var uow = DataFactory.CreateUnitOfWork(TransactionMode.Explicit))
                {
                    if (CreateTransaction)
                    {
                        using (var tx = uow.CreateTransaction())
                        {
                            result = getNext()(input, getNext);
                            if (result.Exception == null)
                                tx.Commit();
                            else
                                tx.Rollback();
                        }
                    }
                    else
                    {
                        result = getNext()(input, getNext);
                    }
                }
            }
            catch (Exception ex)
            {
                result = getNext()(input, getNext);
                result.Exception = ex;
            }
            return result;
        }

        public int Order { get; set; }
        public bool CreateTransaction { get; set; }
    }


Problem is, that this policy injection call handler executed twice when we expect that it only executes once. It took us some time to figure out what caused the problem. The reason was that the InterceptionExtension was registered twice:
  • One time explicitly through registration by using the AddNewExtension<T> method on the Unity container.
     
  • One time implicitly by registering the EnterpriseLibraryCoreExtension which also adds the Interception extension.
After removing the explicit registration everything worked fine. To further improve the solution we started to use the AddNewExtensionIfNotPresent<T> extension method which is available in the Enterprise Library Shared Assembly.

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...