[
https://issues.apache.org/jira/browse/SLING-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255053#comment-16255053
]
Karl Pauls commented on SLING-7241:
-----------------------------------
[~bcsott], oh sorry - I see now that you are talking about using the
ScriptEngineManager directly. I was assuming this would use the sling
scriptengine. [~npeltier], in that case, I agree, while this is related to
problems in SLING-7134 it will not be addressed directly. Sorry for the noice.
[~bcsott], I think the difference you see is due to a ThreadContextClassloader.
Probably that is set to something different in the JMX case as in the others
(maybe worthwhile to figure out what the ThreadContextClassloader is set to in
each case).
> [pipes] Nashorn ScriptEngine in PipeBindings is null
> ----------------------------------------------------
>
> Key: SLING-7241
> URL: https://issues.apache.org/jira/browse/SLING-7241
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Pipes 1.0.4
> Environment: java.runtime.name = Java(TM) SE Runtime Environment
> java.runtime.version = 1.8.0_144-b01
> Reporter: Björn Csott
> Priority: Minor
> Attachments: error.log
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
