GraalVM, skip interpreter mode warning

[yanavasileva]

The following output is printed on start of Tomcat/WildFly pre-packaged distros after we bumped graalvm-sdk version in #4299.
The error is produce on each execution of a script.

Details

20:47:11,532 ERROR [stderr] (MSC service thread 1-6) [To redirect Truffle log output to a file use one of the following options:
20:47:11,533 ERROR [stderr] (MSC service thread 1-6) * '--log.file=<path>' if the option is passed using a guest language launcher.
20:47:11,535 ERROR [stderr] (MSC service thread 1-6) * '-Dpolyglot.log.file=<path>' if the option is passed using the host Java launcher.
20:47:11,564 ERROR [stderr] (MSC service thread 1-6) * Configure logging using the polyglot embedding API.]
20:47:11,566 ERROR [stderr] (MSC service thread 1-6) [engine] WARNING: The polyglot context is using an implementation that does not support runtime compilation.
20:47:11,566 ERROR [stderr] (MSC service thread 1-6) The guest application code will therefore be executed in interpreted mode only.
20:47:11,569 ERROR [stderr] (MSC service thread 1-6) Execution only in interpreted mode will strongly impact the guest application performance.
20:47:11,570 ERROR [stderr] (MSC service thread 1-6) For more information on using GraalVM see https://www.graalvm.org/java/quickstart/.
20:47:11,570 ERROR [stderr] (MSC service thread 1-6) To disable this warning the '--engine.WarnInterpreterOnly=false' option or use the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.
20:47:11,990 ERROR [stderr] (MSC service thread 1-6) [engine] WARNING: The polyglot context is using an implementation that does not support runtime compilation.
20:47:11,991 ERROR [stderr] (MSC service thread 1-6) The guest application code will therefore be executed in interpreted mode only.
20:47:11,993 ERROR [stderr] (MSC service thread 1-6) Execution only in interpreted mode will strongly impact the guest application performance.
20:47:11,996 ERROR [stderr] (MSC service thread 1-6) For more information on using GraalVM see https://www.graalvm.org/java/quickstart/.
20:47:11,997 ERROR [stderr] (MSC service thread 1-6) To disable this warning the '--engine.WarnInterpreterOnly=false' option or use the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.
20:47:12,135 ERROR [stderr] (MSC service thread 1-6) [engine] WARNING: The polyglot context is using an implementation that does not support runtime compilation.
20:47:12,135 ERROR [stderr] (MSC service thread 1-6) The guest application code will therefore be executed in interpreted mode only.
20:47:12,137 ERROR [stderr] (MSC service thread 1-6) Execution only in interpreted mode will strongly impact the guest application performance.
20:47:12,140 ERROR [stderr] (MSC service thread 1-6) For more information on using GraalVM see https://www.graalvm.org/java/quickstart/.
20:47:12,141 ERROR [stderr] (MSC service thread 1-6) To disable this warning the '--engine.WarnInterpreterOnly=false' option or use the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.
20:47:12,147 ERROR [stderr] (MSC service thread 1-6) [engine] WARNING: The polyglot context is using an implementation that does not support runtime compilation.
20:47:12,148 ERROR [stderr] (MSC service thread 1-6) The guest application code will therefore be executed in interpreted mode only.
20:47:12,149 ERROR [stderr] (MSC service thread 1-6) Execution only in interpreted mode will strongly impact the guest application performance.
20:47:12,152 ERROR [stderr] (MSC service thread 1-6) For more information on using GraalVM see https://www.graalvm.org/java/quickstart/.
20:47:12,153 ERROR [stderr] (MSC service thread 1-6) To disable this warning the '--engine.WarnInterpreterOnly=false' option or use the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.
20:47:12,232 ERROR [stderr] (MSC service thread 1-6) [engine] WARNING: The polyglot context is using an implementation that does not support runtime compilation.
20:47:12,232 ERROR [stderr] (MSC service thread 1-6) The guest application code will therefore be executed in interpreted mode only.
20:47:12,234 ERROR [stderr] (MSC service thread 1-6) Execution only in interpreted mode will strongly impact the guest application performance.
20:47:12,237 ERROR [stderr] (MSC service thread 1-6) For more information on using GraalVM see https://www.graalvm.org/java/quickstart/.
20:47:12,238 ERROR [stderr] (MSC service thread 1-6) To disable this warning the '--engine.WarnInterpreterOnly=false' option or use the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.
20:47:12,243 ERROR [stderr] (MSC service thread 1-6) [engine] WARNING: The polyglot context is using an implementation that does not support runtime compilation.
20:47:12,245 ERROR [stderr] (MSC service thread 1-6) The guest application code will therefore be executed in interpreted mode only.
20:47:12,250 ERROR [stderr] (MSC service thread 1-6) Execution only in interpreted mode will strongly impact the guest application performance.
20:47:12,251 ERROR [stderr] (MSC service thread 1-6) For more information on using GraalVM see https://www.graalvm.org/java/quickstart/.
20:47:12,251 ERROR [stderr] (MSC service thread 1-6) To disable this warning the '--engine.WarnInterpreterOnly=false' option or use the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.

Acceptance Criteria (Required on creation)`

• Revert graalvm-sdk update.
• system out logs are not shown in pre-packaged distros

Hints

• When -Dpolyglot.engine.WarnInterpreterOnly=false is passed to the script engine, the warnings are not displayed.
• passing the following args, the warnings are not displayed:
  --upgrade-module-path=lib\compiler-21.3.11.jar;ib\compiler-management-21.3.11.jar
  But that means we need to adding two more dependencies, as we haven't used those two libraries so far.

Links

• Bump org.graalvm.sdk:graal-sdk to a version >= 21.3.10 #4299
• https://www.graalvm.org/latest/reference-manual/js/FAQ/#warning-implementation-does-not-support-runtime-compilation
• Discussion: https://camunda.slack.com/archives/C036ZURJFMX/p1724658546233539

Breakdown

Pull Requests

Beta Give feedback

1. chore(deps): revert to graalvm 21.1.0 #4562
   bot:java-dependency-check ci:all-as ci:webapp-integration +3
   
2. https://github.com/camunda/camunda-bpm-platform-maintenance/pull/1276
3. https://github.com/camunda/camunda-bpm-platform-maintenance/pull/1277
4. https://github.com/camunda/camunda-bpm-platform-maintenance/pull/1278

Dev2QA handover

• Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

[yanavasileva]

Findings:

• I didn't manage to apply the skip warning flag in

  camunda-bpm-platform/engine/src/main/java/org/camunda/bpm/engine/impl/scripting/engine/DefaultScriptEngineResolver.java

  Lines 141 to 158 in 7ba3216

  	protected void configureGraalJsScriptEngine(ScriptEngine scriptEngine) {
  	ProcessEngineConfigurationImpl config = Context.getProcessEngineConfiguration();
  	if (config != null) {
  	if (config.isConfigureScriptEngineHostAccess()) {
  	// make sure Graal JS can provide access to the host and can lookup classes
  	scriptEngine.getContext().setAttribute("polyglot.js.allowHostAccess", true, ScriptContext.ENGINE_SCOPE);
  	scriptEngine.getContext().setAttribute("polyglot.js.allowHostClassLookup", true, ScriptContext.ENGINE_SCOPE);
  	}
  	if (config.isEnableScriptEngineLoadExternalResources()) {
  	// make sure Graal JS can load external scripts
  	scriptEngine.getContext().setAttribute("polyglot.js.allowIO", true, ScriptContext.ENGINE_SCOPE);
  	}
  	if (config.isEnableScriptEngineNashornCompatibility()) {
  	// enable Nashorn compatibility mode
  	scriptEngine.getContext().setAttribute("polyglot.js.nashorn-compat", true, ScriptContext.ENGINE_SCOPE);
  	}
  	}
  	}

  • errors: failed to set graal-js option "polyglot.js.allowHostAccess": js context is already initialized
• The flag can be add to the jvm args on start but that means we need to add it for all environments.
• An alternative might be to add the GraalVM compiler for better performance. That will require new dependencies.

Decision: we revert the update and do more detailed investigation on how to handle the warnings for the next set of patches.

[yanavasileva]

After downport, the warnings are gone. On CI they can be observed in webapp-IT stages.