Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Sending Request to Dispatcher not Publish

Avatar

Avatar
Validate 10
Level 2
sunitac70336244
Level 2

Likes

7 likes

Total Posts

65 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 1
View profile

Avatar
Validate 10
Level 2
sunitac70336244
Level 2

Likes

7 likes

Total Posts

65 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 1
View profile
sunitac70336244
Level 2

07-08-2019

Dear All,

I have an below requirement.

When I will request one page for example (http://localhost/content/we-retail/us/en/women.html) then the request will go to dispatcher cache not to Publish and

It request will display the page from Dispatcher cache not from publish.

Can anybody put some lights how can I achieve this.

I am using AEM 6.4

Thanks in advance.

View Entire Topic

Avatar

Avatar
Give back 300
MVP
Gaurav-Behl
MVP

Likes

243 likes

Total Posts

1,145 posts

Correct Reply

281 solutions
Top badges earned
Give back 300
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Give back 300
MVP
Gaurav-Behl
MVP

Likes

243 likes

Total Posts

1,145 posts

Correct Reply

281 solutions
Top badges earned
Give back 300
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile
Gaurav-Behl
MVP

13-08-2019

Use case #1 is not an issue as you mentioned because it picks up the cached content from dispatcher, however, the hostname and port# in dispatcher.any file should be of the "publish server" that is supposed to serve the content to dispatcher and not apache server's.

You have configured 'statfileslevel' to 5 which I assume is intentional based on your app architecture/design.

When I will change my page in author http://localhost/content/trainingproject/en.html and activate the page then the updated page will store in the dispatcher cache (the /docroot). But in my case it is not storing in dispatcher cache.

I assume that you understand how dispatcher connects to the publish server, pulls the content from publish server because it is a reverse proxy and caches it as and when required. Check "How Dispatcher returns Documents"  @ Overview  in case you need more details.

When you activate the modified page, it would reside in the publish server but not in the dispatcher cache until the dispatcher requests for that updated page from publish server. This means it needs to know the publish server's IP/hostname and port to connect and pull the latest content. Render section (/rend01) of dispatcher.any serves this purpose to enable the communication between dispatcher and publish server. 

In your case #2, it is not storing updated content in dispatcher because the connection between dispatcher & publish server is broken. Yes, you're correct.

By default, the very first request would go to publish server and all subsequent requests for same content should be served from dispatcher cache in an ideal scenario.