AEM Publisher throwing maintenance exception in logs | Community
Skip to main content
A
Ashish_Ranjan1
Level 2
April 29, 2020
Solved

AEM Publisher throwing maintenance exception in logs

  • April 29, 2020
  • 3 replies
  • 8381 views

We have two AEM Publishers and the below exception is continuously thrown on both the publishers.

 

29.04.2020 16:50:21.804 *INFO* [qtp279028224-11690] log.request 29/Apr/2020:16:50:21 +0000 [130007] -> GET /libs/granite/operations/config/maintenance/granite:daily.infinity.json HTTP/1.1
 
The maintenance jobs for daily and weekly is configured and working fine. Any other reason why this might be happening?
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 vish.dhaliwal

Hello Ashish,

It looks like it's trying to find the config for the task using the old location, instead of the new location /conf/global/settings/granite/operations/maintenance/granite_daily. The libs path does not exist, hence the 404.

The request was used in lower versions of AEM like AEM 6.2 to get maintenance task info, these request would not have any impact on the maintenance task run on AEM 6.3 and above.

Regards,

Vishu

3 replies

Singaiah_Chintalapudi
Singaiah_Chintalapudi
Level 7
April 29, 2020

These are just "INFO" logs. Are you noticing these entries frequently on your logs?

    A
    Ashish_Ranjan1Author
    Level 2
    April 30, 2020

    Yes these are frequently in our logs. And due to this request combined with ACS Commons we noticed that The call that AEM is getting, that call in itself is 404 always, checked it on vanilla server.

     

    Since the call is 404, it would invoke your error handler JSP.. and the vanity check code is throwing some code error, when the incoming URL pattern is: /libs/granite/operations/config/maintenance/granite:daily.infinity.json

     

    So we had to wrap the 404.jsp to catch the exception.

     

    sunjot16
    Adobe Employee
    sunjot16Adobe Employee
    Adobe Employee
    April 29, 2020

    This is just an INFO log. You shouldn't be worried about it. You can ignore it.

    A
    Ashish_Ranjan1Author
    Level 2
    April 30, 2020
    Yes these are frequently in our logs. And due to this request combined with ACS Commons we noticed that The call that AEM is getting, that call in itself is 404 always, checked it on vanilla server. Since the call is 404, it would invoke your error handler JSP.. and the vanity check code is throwing some code error, when the incoming URL pattern is: /libs/granite/operations/config/maintenance/granite:daily.infinity.json So we had to wrap the 404.jsp to catch the exception.
    V
    Adobe Employee
    vish.dhaliwalAdobe EmployeeAccepted solution
    Adobe Employee
    April 30, 2020

    Hello Ashish,

    It looks like it's trying to find the config for the task using the old location, instead of the new location /conf/global/settings/granite/operations/maintenance/granite_daily. The libs path does not exist, hence the 404.

    The request was used in lower versions of AEM like AEM 6.2 to get maintenance task info, these request would not have any impact on the maintenance task run on AEM 6.3 and above.

    Regards,

    Vishu

      A
      Ashish_Ranjan1Author
      Level 2
      April 30, 2020
      This is happening in AEM 6.5.2 . Due to this request combined with ACS Commons we noticed that The call that AEM is getting, that call in itself is 404 always, checked it on vanilla server. Since the call is 404, it would invoke your error handler JSP.. and the vanity check code is throwing some code error, when the incoming URL pattern is: /libs/granite/operations/config/maintenance/granite:daily.infinity.json So we had to wrap the 404.jsp to catch the exception.
      Terms & ConditionsAccessibility statement

      Loading footer...