Using Nashorn with OpenJDK 17 and IdP 4.3.1
Vlad Mencl
vladimir.mencl at reannz.co.nz
Wed Feb 21 03:19:41 UTC 2024
Thanks for the help.
I now "solved it" ... with an explanation I'm still not 100% happy with,
but it works now.
I was running Tomcat with -Dnashorn.args=--no-deprecation-warning
- which I added to reduce log pollution with warnings about Nashorn
being removed in future JDK releases.
With all sane attempts failing (I had the same behaviour also on Debian
12 with Tomcat 10), I thought I'd remove this from my environment ...
and then Nashorn started loading normally.
Sharing here in case someone else runs into it too....
Thanks for all the help and pointers provided.
Cheers,
Vlad
On 21/02/24 10:08, Cantor, Scott wrote:
> [You don't often get email from cantor.2 at osu.edu. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
>> Anything where these plugins would be different in how they expose the
>> ScriptEngine to Java's Service Loader ?
>
> Rhino is more our code than Nashorn, but no, I don't really know. I'd file a bug, but I know we add Nashorn when we run tests and that's all working, so I still have my suspicions you have a class loading problem somewhere.
>
> -- Scott
>
>
--
Vladimir Mencl
Lead Software Engineer
Research & Education
Advanced Network NZ Ltd
E vladimir.mencl at reannz.co.nz
www.reannz.co.nz
More information about the users
mailing list