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"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:noNamespaceSchemaLocation="schemas/cd_storage_conf.xsd">
  <Global>
    <ObjectCache Enabled="true">
      <Policy Type="LRU" Class="com.tridion.cache.LRUPolicy">
        <Param Name="MemSize" Value="512mb"/>
      </Policy>

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

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
            //cache.Remove(key);
        }
    }
}

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().



Comments

Popular posts from this blog

Scaling Policies

This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the

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: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , 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

Toolkit - Dynamic Content Queries

This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio