Comments on: Attack of the AEM Link Checker!!

By: Dan Klco

Dan Klco — Thu, 26 Sep 2019 15:02:46 +0000

In reply to Justin Allen. It shouldn't pose an issue, but as with any production system, I would be cautious. If you have multiple instances, I would definitely do it one at a time and even consider taking them temporarily out of rotation so that the link checker for sure won't be reading / writing to the node structure while you're doing the deletion.

By: Justin Allen

Justin Allen — Thu, 26 Sep 2019 04:23:45 +0000

Hi Dan ,
I am also seeing similar issues in our 6.3 Prod environment for the linkchecker. Our aem instance hosts 4 sites and each of those sites have external links in the footers on the page and additionally our content creators seem to generate external links our sites which should be made relative.
As of now I am approaching to add the OSGi pattern filter to avoid linkchecker going over the externalized links generated by our content creators which should be externalized and am also thinking of trying to add markup tags for aem to skip processing the footer external links.
I am considering deleting the nodes (associated with the external urls that are erroing) that are also generating under /var/linkchecker as this is the cached links that are checked so that linkchecker doesn’t iterate through them. Any thoughts on removing this excess nodes that we will no longer check?
Thanks

By: Arvind

Arvind — Tue, 30 Jul 2019 12:24:00 +0000

Hey Dan,
Great details in the article. More or less I am seeing the same issue. But do you think, what ever the AEM version is, does the performance issue still remains the same with the link checker, if we have large content?
Thanks,
Arvind