AEM Publisher throwing maintenance exception in logs | Community
Skip to main content
Ashish_Ranjan1
Level 2
Apr 29, 2020 5:20 PM UTC
Solved

AEM Publisher throwing maintenance exception in logs

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.
vish.dhaliwalAccepted solution
Employee
Apr 30, 2020 12:46 PM UTC

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

View reply

7 replies

vish.dhaliwalAccepted solution
Employee
Apr 30, 2020 12:46 PM UTC

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

Translate
    Ashish_Ranjan1Author
    Level 2
    Apr 30, 2020 12:51 PM UTC
    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.
    Translate
    sunjot16
    sunjot16
    Employee
    Apr 29, 2020 8:02 PM UTC

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

    Translate
    Ashish_Ranjan1Author
    Level 2
    Apr 30, 2020 12:49 PM UTC
    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.
    Translate
    Singaiah_Chintalapudi
    Singaiah_Chintalapudi
    Level 7
    Apr 29, 2020 6:40 PM UTC

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

    Translate
      Ashish_Ranjan1Author
      Level 2
      Apr 30, 2020 6:41 AM UTC

      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.

       

      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...