Subijay contacted me on GitHub too[0], and I suggested they retest with Java 16 or newer, suspecting this might be a duplicate of JDK-8198540[1] which was fixed in Java 16. He confirmed there that the issue indeed goes away with Java 17, I’ll take it as a confirmation it was indeed a duplicate of 8198540.
Attila. — [0] https://github.com/szegedi/dynalink/issues/15 [1] https://bugs.openjdk.org/browse/JDK-8198540 > On 4 Oct 2024, at 10:57, Subijay Bhattacharya <[email protected]> wrote: > > Hi Nashorn team, > > We have an enterprise application running on wildfly and using open JDK > 11.0.22. We use Camunda for business process flow and Camunda uses Nashorn. > We are impacted by the bug https://bugs.openjdk.org/browse/JDK-8229011 > > Could someone please let me know if there is a plan to fix this? > > I know nashorn was removed from core JDK in jdk15. and now it is maintained > in GitHub. > If we pick the latest Nashorn from GitHub will it have the fix. I did not > seem to find the right information on the fix. > > Thanks in advance and appreciate your help on this. > > -Subijay
