Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-7241

[pipes] Nashorn ScriptEngine in PipeBindings is null

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • 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
    • Labels:
      None
    • Environment:
      java.runtime.name = Java(TM) SE Runtime Environment
      java.runtime.version = 1.8.0_144-b01

      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

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              npeltier Nicolas Peltier
              Reporter:
              bcsott Björn Csott

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment