ProxyAsyncScriptableFactory uses the deprecated asynchronous API provided by the 'granite' namespace. Please refactor the script to use the synchronous API provided by the org.apache.sling.scripting.javascript bundle. | Community
Skip to main content
gayatrik8153299
Level 2
July 29, 2020
Solved

ProxyAsyncScriptableFactory uses the deprecated asynchronous API provided by the 'granite' namespace. Please refactor the script to use the synchronous API provided by the org.apache.sling.scripting.javascript bundle.

  • July 29, 2020
  • 2 replies
  • 3186 views

Hi,

We are getting some warning messages in logs.

 

28.07.2020 01:15:11.225 *WARN* [10.43.32.87 [1595898911218] GET /content/diagnostics/be/en/products/product-category/clinical-chemistry-and-immunochemistry.html HTTP/1.1] org.apache.sling.scripting.sightly.js.impl.jsapi.ProxyAsyncScriptableFactory Script /libs/wcm/foundation/components/page/head.js uses the deprecated asynchronous API provided by the 'granite' namespace. Please refactor the script to use the synchronous API provided by the org.apache.sling.scripting.javascript bundle.

 

Could you please let us know how to resolve this.

we have been upgraded from aem 6.2 to 6.4

is this upgrade issue or we need to update head.js file or any API.

 

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 user05162

This is expected and by default, there is a logger to exclude these kind of warnings from error.log. See below:

 

If similar logger does not exist under /system/console/slinglog. Go ahead and create one and make sure the log level is set to ERROR so that these warnings are not shown in error.log

 

2 replies

ChitraMadan
Community Advisor
Community Advisor
July 29, 2020
gayatrik8153299
Level 2
July 29, 2020
Yes i could see..can i know is the issue resolved?
user05162Adobe EmployeeAccepted solution
Adobe Employee
July 29, 2020

This is expected and by default, there is a logger to exclude these kind of warnings from error.log. See below:

 

If similar logger does not exist under /system/console/slinglog. Go ahead and create one and make sure the log level is set to ERROR so that these warnings are not shown in error.log