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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

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.

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...