Flush page and re build cache in all dispatchers

hi @veerareddyc1015, you can force the behaviour into the dispatcher with a POST call

as explained here.You can set up a scheduler for each publishing instance to trigger a POST call, ensuring that all dispatchers in the infrastructure will rebuild the cache. The scheduler must compute all the links for the website, similar to a sitemap, so that these links can be included in the body of the POST request.

if you are looking for auto flush based on scheduled frequencies, OSGI config can be helpful

1. Create OSGI config that gets reflected in Felix Server(/system/console) --> Configuration tab

DispatcherCacheRefresherConfig.java

import org.osgi.service.metatype.annotations.ObjectClassDefinition;
import org.osgi.service.metatype.annotations.AttributeDefinition;

@ObjectClassDefinition(name = "Dispatcher Cache Refresher Config")
public @interface DispatcherCacheRefresherConfig {

@AttributeDefinition(name = "Page Path", description = "Path of the page to flush and regenerate")
String pagePath();

@AttributeDefinition(name = "Dispatcher Flush URL", description = "URL used to flush the dispatcher cache")
String flushUrl();

@AttributeDefinition(name = "Cron Expression", description = "Cron expression for scheduler")
String schedulerExpression() default "0 0/30 * * * ?"; // every 30 min

@AttributeDefinition(name = "Enabled", description = "Enable or disable the job")
boolean enabled() default true;
}


2. Create a Scheduler to execute job based on the config parameters defined in above OSGI Conf

DispatcherCacheRefresher.java

import org.osgi.service.component.annotations.*;
import org.osgi.service.metatype.annotations.Designate;
import org.apache.sling.commons.scheduler.Scheduler;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import java.net.HttpURLConnection;
import java.net.URL;

@8220494(service = Runnable.class, immediate = true)
@Designate(ocd = DispatcherCacheRefresherConfig.class)
public class DispatcherCacheRefresher implements Runnable {

private final Logger log = LoggerFactory.getLogger(this.getClass());

@3214626
private Scheduler scheduler;

private DispatcherCacheRefresherConfig config;
private static final String osgiJob = "dispatcher-cache-refresher";

@580286
@9182423
protected void activate(DispatcherCacheRefresherConfig config) {
this.config = config;

if (config.enabled()) {
try {
scheduler.remove(osgiJob);
scheduler.addJob(osgiJob, this, null, config.schedulerExpression(), true);
log.info("Dispatcher Cache Refresher job scheduled.");
} catch (Exception e) {
log.error("Error scheduling job", e);
}
}
}

@3038739
protected void deactivate() {
scheduler.remove(osgiJob);
}

@9944223
public void run() {
try {
flushDispatcherCache(config.flushUrl());
regeneratePage(config.pagePath());
} catch (Exception e) {
log.error("Error in dispatcher cache refresher job", e);
}
}

private void flushDispatcherCache(String flushUrl) throws Exception {
log.info("Flushing Dispatcher Cache at {}", flushUrl);
HttpURLConnection con = (HttpURLConnection) new URL(flushUrl).openConnection();
con.setRequestMethod("GET");
int responseCode = con.getResponseCode();
log.info("Flush response code: {}", responseCode);
}

private void regeneratePage(String pagePath) throws Exception {
String url = "http://localhost:4503" + pagePath + ".html"; // assuming publish or internal dispatcher
log.info("Regenerating page by requesting: {}", url);
HttpURLConnection con = (HttpURLConnection) new URL(url).openConnection();
con.setRequestMethod("GET");
int responseCode = con.getResponseCode();
log.info("Page regeneration response code: {}", responseCode);
}
}

Now, 

• Deploy the OSGi service.

• Configure the values in system/console/configmgr

• Verify cache files are removed and regenerated under the dispatcher docroot(folder created in your webtop/mac/server
  
  Hope this gives info you are looking for.
  
  Thanks
  Kiran Buthpur
  
  

@veerareddyc1015 

Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!