Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.

Delivery of "Cached" Messages

Avatar

Former Community Member
I'm trying to set up a destination that will deliver "cached" messages to clients that may have connected/subscribed to the destination after a particular message was put into the destination. For example



9:00 client A suscribes

9:05 "blah" gets put into the destination, client A gets the message

9:06 client B suscribes and also gets the cached message "blah"



I've tried to set the following



ServerSettings serverSettings = new ServerSettings();

serverSettings.setMaxCacheSize(1000);

serverSettings.setMessageTTL(0);

serverSettings.setDurable(false);

destination.setServerSettings(serverSettings);



According to the docs, the last 1000 messages should be cached and they will live until the server shutdown. However my client B doesn't get delayed delivery of the message that was pumped in before it came on line.



I want to do this without a JMS queue. If the settings I'm using aren't meant for this, what are they suspose to do?? And what should I be doing to enable the senario I described.



Thanks, KT
1 Reply

Avatar

Former Community Member
Hi,



Is there anyone who is familliar with this part of the lcds? Any help is appreciated.



KT