Skip to main content

Usage and Configuration of the .NET Cache Invalidation Callback

In the previous post, I described a way to intercept in .NET cache invalidate events generated in Java. This post presents the way to configure, use and write your own code that handles the Java generated invalidate events.

The entire code presented here is available on this blog's GIT repository. Link here.

Java Stuff

Modify your cd_storage_conf.xml (located in your .net website /bin/conf folder), and reference class com.tridion.cache.DD4TDependencyTracker as the Feature inside node ObjectCache:

<Configuration Version="7.1"
    <ObjectCache Enabled="true">
      <Policy Type="LRU" Class="com.tridion.cache.LRUPolicy">
        <Param Name="MemSize" Value="512mb"/>

          <Feature Type="DependencyTracker" Class="com.tridion.cache.DependencyTracker"/>
        <Feature Type="DependencyTracker" Class="com.tridion.cache.DD4TDependencyTracker"/>

Copy file cache-notifier.jar to your website's /bin/lib folder.

.NET Stuff

In your .NET project, copy DLL Com.MihaiConsulting.CacheNotifier.dll and reference it from your project.

Create a class that implements Com.MihaiConsulting.Cache.ICacheInvalidator interface:

using Com.MihaiConsulting.Cache;

namespace MyCacheInvalidator.Example
    public class MyCacheInvalidator : ICacheInvalidator
        public MyCacheInvalidator()
            CacheNotifier.Instance.Invalidator = this;

        public void Invalidate(string key)
            //perform your own cache removal here

This class must be set as the 'Invalidator' to call when a message comes from the CacheNotifier on the Java side. The simplest way to achieve this is to use some Dependency Injection framework and set this instance as the Invalidator for the .NET proxy Com.MihaiConsulting.Cache.CacheNotifier. In the absence of such a DI framework, the simplest solution is to set 'this' as the Invalidator at the moment of constructing the instance:

            CacheNotifier.Instance.Invalidator = this;

At this point, the method Invalidate of class MyCacheInvalidator will be called when a message is sent to the DD4TDependencyTracker in Java for method processRemove().


Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: I stumbled upon the following post from 2008 (!!!), , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven