[SLING-7241] [pipes] Nashorn ScriptEngine in PipeBindings is null

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Pipes 1.0.4
• Fix Version/s: Pipes 2.0.2
• Component/s: Extensions
• Environment: java.runtime.name = Java(TM) SE Runtime Environment ; java.runtime.version = 1.8.0_144-b01
• External issue URL: https://github.com/bcsott/migration-tool
• Assignee: Nicolas Peltier
• Reporter: Björn Csott
• Created: 14/Nov/17 21:00
• Updated: 24/Apr/18 13:30
• Resolved: 24/Nov/17 10:03

Description

Under some unclear circumstances the ScriptEngine in PipeBindings does not get initialized.
There is a solution out there to attach Nashorn to the system bundle. Appart from that I was able to fix it by using a different constructor: ScriptEngineManager(null).

The issue can be reproduced by deploying https://github.com/bcsott/migration-tool

When it fails the following is written to stderror.log:
ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory:
Provider jdk.nashorn.api.scripting.NashornScriptEngineFactory not found

Issue Links

• relates to: SLING-7134 Script execution order is not deterministic on Java 9 and nashorn engine is missing in java8
• links to: GitHub Pull Request #1
• links to: GitHub Pull Request #2