AEM author throws 404



Hi ,


Recently aem author instances was not accessible and was throwing 404 .But after restart it worked fine for next few days and issue happened agin today.Also please note that stoping the aem service took long time more than 10 min.


Now can anyone please suggest what could be the issue.Or suggest us what should we check if the issue arise again.


Browser output/error:

Not Found (404)
The requested URL /libs/granite/core/content/login.html resulted in an error in

Request Progress:
0 TIMER_START{Request Processing}
1 COMMENT timer_end format is {<elapsed microseconds>,<timer name>} <optional message>
15 LOG Method=GET, PathInfo=null
17 TIMER_START{handleSecurity}
1320 TIMER_END{1302,handleSecurity} authenticator returns true
1590 TIMER_START{ResourceResolution}
2751 TIMER_END{1160,ResourceResolution} URI=/libs/granite/core/content/login.html resolves to Resource=JcrNodeResource, type=granite/core/components/login, superType=null, path=/libs/granite/core/content/login
2759 LOG Resource Path Info: SlingRequestPathInfo: path='/libs/granite/core/content/login', selectorString='null', extension='html', suffix='null'
2759 TIMER_START{ServletResolution}
2762 TIMER_START{resolveServlet(/libs/granite/core/content/login)}
2774 TIMER_END{10,resolveServlet(/libs/granite/core/content/login)} Using servlet
2775 TIMER_END{15,ServletResolution} URI=/libs/granite/core/content/login.html handled by
2778 LOG Applying Requestfilters
2782 LOG Calling filter: com.adobe.granite.resourceresolverhelper.impl.ResourceResolverHelperImpl
2787 LOG Calling filter:
2801 LOG Calling filter: com.adobe.granite.csrf.impl.CSRFFilter
2813 LOG Calling filter:
2819 LOG Calling filter: com.adobe.granite.httpcache.impl.InnerCacheFilter
2832 LOG Calling filter:
2840 LOG Calling filter: com.adobe.cq.mcm.campaign.servlets.CampaignCopyTracker
2900 LOG Calling filter: com.adobe.cq.history.impl.HistoryRequestFilter
3184 LOG Calling filter:
3206 LOG Calling filter: com.adobe.cq.wcm.core.components.internal.servlets.CoreFormHandlingServlet
3219 LOG Calling filter: com.adobe.granite.optout.impl.OptOutFilter
3249 LOG Calling filter:
3262 LOG Calling filter:
3272 LOG Calling filter:
3283 LOG Calling filter:
3286 LOG Calling filter:
3289 LOG Calling filter:
3300 LOG Calling filter:
3313 LOG Calling filter:
3317 LOG Calling filter: com.adobe.granite.requests.logging.impl.RequestLoggerImpl
3330 LOG Calling filter:
3401 LOG Calling filter:
3423 LOG Calling filter:
3426 LOG Calling filter:
3440 LOG Calling filter:
3455 LOG Applying Componentfilters
3457 LOG Calling filter:
3468 LOG Calling filter:
3480 LOG Calling filter:
3683 LOG Calling filter: ca.bellmedia.aem.commons.filters.SetViewPreferencesFilter
3737 LOG Calling filter:
3769 LOG No renderer for extension html
3802 LOG Applying Error filters
3804 LOG Calling filter:
3815 LOG Calling filter:
3830 TIMER_START{handleError:status=404}
4496 TIMER_END{665,handleError:status=404} Using handler
5706 LOG Found processor for post processing ProcessorConfiguration: {contentTypes=[text/html], order=1, active=true, valid=true, processErrorResponse=true, pipeline=(generator=Config(type=htmlparser, config={}), transformers=(Config(type=linkchecker, config={}), Config(type=versioned-clientlibs, config={}), serializer=Config(type=htmlwriter, config={}))}
6561 TIMER_END{6561,Request Processing} Dumping SlingRequestProgressTracker Entries


11.08.2020 14:05:13.114 *INFO* [ [1597169112370] GET /projects.html/content/projects HTTP/1.1] com.adobe.granite.ui.clientlibs.impl.HtmlLibraryManagerImpl detecte
d [JS, CSS] library: /libs/dam/cfm/admin/clientlibs/v2/assoccontent, sourced from 15 files.
Apache Sling




Accepted Solutions (1)

Accepted Solutions (1)



With the latest version of AEM 6.5.* , when ever a deployment is happening in OSGI. I am observing that when ever i am deploying a bundle , i can see that at-least for 20 mins AEM instance is non responsive.


Do check the error.log with tail command when it is not responsive. If you observe that bundles are restarting then there is no need to restart AEM instance. 

Answers (1)

Answers (1)




To add to this, also capture a series of 10 thread dumps (1 every 10 seconds) when you see slowness along with the top -H output such that you can map thread id at your end in thread dump. See here [1].