dd4t / dd4t-cachechannel Goto Github PK

After the upgrade to Tridion 9, the invalidation of DCPs stopped working. The reason is that the custom serializer changes the keys of the cache event. This is not a good idea, because the content service needs to use the same connector and it must know for sure that the keys are the same as with the normal connector.

I have implemented JMS based cache invalidation mechanism using Apache MQ, application is MVC.NET 4.0 application, I found there is lot of inconsistent behavior while we try to invalidate the cache, both Tridion Object and DD4T cache are enabled.

Following is the observation

MVC.NET does not support JMS object messaging so a custom TextJMSCacheChannelConnector class needs to be used (https://github.com/dd4t/dd4t-cachechannel) to handle text messages at both deployer and website level

If we implement TextJMSCacheChannelConnector class Tridion Object Cache does not gets invalidated as HandleMessage method is not implemented in TextJMSCacheChannelConnector and HandleMessage method in JMSCacheChannelConnector class is not handling Text Message and throwing error "Message Type not supported"

If Default JMSCacheChannelConnector is used then Tridion object cache does get invalidated, however DD4T cache does not get invalidated because it uses TextJMSCacheChannelConnector and it is not capable of handling object messaging.

I think we might need to implement a HandleMessage method in TextJMSCacheChannelConnector to handle text based messages as well.

Regards, Sameer