Level 2

Solved

Dispatcher | Cache invalidation not working locally

Forum|Forum|9 years ago
May 16, 2016
7 replies
9096 views

Dear AEM community,

I faced a problem when i configured a dispatcher cache flush.

After enabling the flush agent, clicking test logs this:

Replication test to http://localhost:8080/dispatcher/invalidate.cache

18.02.2015 12:00:11 - Create new HttpClient for Dispatcher Flush 18.02.2015 12:00:11 - * HTTP Version: 1.1 18.02.2015 12:00:11 - adding header: CQ-Action:Test 18.02.2015 12:00:11 - adding header: CQ-Handle:/content 18.02.2015 12:00:11 - adding header: CQ-Path:/content 18.02.2015 12:00:11 - deserialize content for delivery 18.02.2015 12:00:11 - No message body: Content ReplicationContent.VOID is empty 18.02.2015 12:00:11 - Sending GET request to http://localhost:8080/dispatcher/invalidate.cache 18.02.2015 12:00:11 - sent. Response: 404 Not Found 18.02.2015 12:00:11 - Replication (TEST) of /content not successful. Conversation follows 18.02.2015 12:00:11 - ------------------------------------------------ 18.02.2015 12:00:11 - Sending message to localhost:8080 18.02.2015 12:00:11 - >> GET /dispatcher/invalidate.cache HTTP/1.0 18.02.2015 12:00:11 - >> CQ-Action: Test 18.02.2015 12:00:11 - >> CQ-Handle: /content 18.02.2015 12:00:11 - >> CQ-Path: /content 18.02.2015 12:00:11 - >> Referer: about:blank 18.02.2015 12:00:11 - >> Content-Length: 0 18.02.2015 12:00:11 - >> Content-Type: application/octet-stream 18.02.2015 12:00:11 - -- 18.02.2015 12:00:11 - << HTTP/1.1 404 Not Found 18.02.2015 12:00:11 - << Date: Wed, 18 Feb 2015 01:00:11 GMT 18.02.2015 12:00:11 - << Server: Apache/2.4.7 (Unix) Communique/4.1.5 18.02.2015 12:00:11 - << Content-Length: 225 18.02.2015 12:00:11 - << Content-Type: text/html; charset=iso-8859-1 18.02.2015 12:00:11 - << 18.02.2015 12:00:11 - << <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> 18.02.2015 12:00:11 - << <html><head> 18.02.2015 12:00:11 - << <title>404 Not Found</title> 18.02.2015 12:00:11 - << </head><body> 18.02.2015 12:00:11 - << <h1>Not Found</h1> 18.02.2015 12:00:11 - << <p>The requested URL /dispatcher/invalidate.cache was not found on this server.</p> 18.02.2015 12:00:11 - << </body></html> 18.02.2015 12:00:11 - Message sent. 18.02.2015 12:00:11 - ------------------------------------------------ 18.02.2015 12:00:11 - Replication (TEST) of /content not successful.

Any ideas what is probably not configured properly?

Also when i configured the dispatcher module, i changed the file "dispatcher.any" to "myhost.any".

Maybe the issue above is affected to the path /dispatcher/invalidate.cache or i missed out to configure anything.

Thanks,

Thuong.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by smacdonald2008

Message from support on this:

The dispatcher might not be active on the path /dispatcher/invalidate.cache if DispatcherDeclineRoot 1 and the dispatcher-handler is only enabled for a particular URL location.

Basically the flush request must be received at a path where dispatcher will handle the request. I would request they review the dispatcher.log with debug logging enabled. If the request is not showing in the dispatcher.log then it is some configuration in the web server and they would need to provide their dispatcher configs and web server configs.

smacdonald2008Accepted solution

Level 10

Message from support on this:

The dispatcher might not be active on the path /dispatcher/invalidate.cache if DispatcherDeclineRoot 1 and the dispatcher-handler is only enabled for a particular URL location.

Basically the flush request must be received at a path where dispatcher will handle the request. I would request they review the dispatcher.log with debug logging enabled. If the request is not showing in the dispatcher.log then it is some configuration in the web server and they would need to provide their dispatcher configs and web server configs.

edubey

Level 10

Try to change the URL in by Editing from http://localhost:8080/dispatcher/invalidate.cache to http://localhost:80/dispatcher/invalidate.cache as Apache default works on 80 port

Thanks

T

tinyt6510512Author

Level 2

Dear smacdonald2008, edubey,

Thanks for your support. I resolved by re-configuration httpd.conf

Thank,

Thuong.

swapnan73983825

Level 2

Hi TinyT,

We are also facing the same issue in our application. But the issue is not frequent. Replication works fine for 5 days and it stops after 5th or 6th day. We observed that the replication is blocked at the dispatcher level and we also got the same issue.

Can you please let us know how you have fixed the issue. What configuration changes you have done in httpd.conf?

Thanks,

Swapna

swapnan73983825

Level 2

tinyt6510512 wrote...

Dear smacdonald2008, edubey,

Thanks for your support. I resolved by re-configuration httpd.conf

Thank,

Thuong.

Hi TinyT,

We are also facing the same issue in our application. But the issue is not frequent. Replication works fine for 5 days and it stops after 5th or 6th day. We observed that the replication is blocked at the dispatcher level and we also got the same issue.

Can you please let us know how you have fixed the issue. What configuration changes you have done in httpd.conf?

Thanks,

Swapna

T

tinyt6510512Author

Level 2

Hi Swapna,

We need to double check on the dispatcher.any and we should update

/allowedClients

and added the ip of publish server.

also you can check the docroot configuration.

Thanks,

Thuong.

swapnan73983825

Level 2

Thanks Thuong. But this dispatcher flush works fine for few days and it stops suddenly after 5th or 6th day. Did you faced this issue any time.

Thanks,

Swapna

Replication test to http://localhost:8080/dispatcher/invalidate.cache

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded