Is there any documentation to know all the known issues about dispatcher??

Correctly mentioned by Lokesh, 

Release notes will show you all known issues,

6.0   https://docs.adobe.com/docs/en/aem/6-0/release-notes.html

6.0 SP1  https://docs.adobe.com/docs/en/aem/6-0/release-notes-sp1.html

6.1    https://docs.adobe.com/docs/en/aem/6-1/release-notes.html

6.1 SP1  https://docs.adobe.com/docs/en/aem/6-1/release-notes-sp1.html

6.2  https://docs.adobe.com/docs/en/aem/6-2/release-notes.html

For rest, File a daycare ticket.

Thanks and Regards

Kautuk Sahni

Usually in the release-notes file you find an overview of the fixed issues.

Are you facing issues?

Feike Visser wrote...

Usually in the release-notes file you find an overview of the fixed issues.

Are you facing issues?

 

We want to understand one behavior which dispatcher can not serve the required rendition that for an image we have renditions along with original content.

When first time we request for original or any rendition of an image dispatcher serve the them as expected but next time if we request any one of them it will not serve the requested  rendition instead of it's throwing 404 error page.

Is that bug at dispatcher side?

Thanks,

Kishore

Hi,

please increase the loglevel of the dispatcher to the maximum ("3"), restart the dispatcher, clear the cache and then repeat your requests again. Then the logs contain many more details.

Note: On Unix a "file" is either a regular file or a directory. Depending on the order of requests asset.jpg is either a file (when "/content/dam/asset.jpg" is requested first) or a directory (if "/content/dam/asset.jpeg/renditions/myrendition.jpg" is requested first).

Jörg

Thanks Jorg.

Based on your reply i have one question ,if suppose i request '/content/dam/asset.jpg' will this be treated as file or directory.If dispatcher can not find it as file,it throws 404 exception.

Is my understanding correct??

If yes,how can we fix this issue?

Thanks,

Kishore

As Jorg indicated, increase the loglevel so we can see what is causing the 404.

The logs you can see in the dispatcher.log

I doubt it is a bug, usually it is some config that needs to be adjusted

Hi,

I was thinking of this scenario: Suppose you have 2 requests:

1. /content/dam/asset.jpg
2. /content/dam/asset.jpg/rendition/subrendition.jpg

Depending on the order of these requests you might have these scenarios:

• first request 1, then request 2: /content/dam/asset.jpg is then a file in the dispatcher cache; therefor /content/dam/asset.jpg/rendition/subrendition.jpg cannot be created (because asset.jpg should be a directory then); request 2 will then always get served from the AEM instance.
• first request 2, then request 1: /content/dam/asset.jpg is a directory then, and /content/dam/asset.jpg cannot be cached (asset.jpg is a directory). request 1 will always be served from the AEM instance.

This is a totally valid behaviour and not a bug in dispatcher, but rather a glitch in your application. When you have to adress both the asset and a subrendition, you should change the URL of the asset to something like /content/dam/asset.jpeg/rendition/rendition1.jpg, then asset.jpg will be always a directory and there's not a problem.

In any case there should never be a 404 in this case.

So please increase the loglevel, perform the tests and come back if you are unsure howto interprete the results.

Jörg