Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no script engine found with name 'JavaScript #170

Closed
coderzpw1 opened this issue Jan 5, 2022 · 5 comments · Fixed by #332
Closed

no script engine found with name 'JavaScript #170

coderzpw1 opened this issue Jan 5, 2022 · 5 comments · Fixed by #332
Labels
bug Something isn't working

Comments

@coderzpw1
Copy link

What is the reason for reporting "no script engine found with name 'JavaScript'"?

@saig0 saig0 added the bug Something isn't working label Jan 6, 2022
@saig0
Copy link
Contributor

saig0 commented Jan 6, 2022

@coderzpw1 please share more details about your environment.

How do you run the Zeebe worker?
Do you use the provided Docker image?

It works for me with the latest Docker image zeebe-script-worker:1.1.0.

@coderzpw1
Copy link
Author

This error is caused by the high JDK version. Now it's OK to change to jdk11

@saig0
Copy link
Contributor

saig0 commented Jan 11, 2022

This error is caused by the high JDK version.

True. JavaScript is removed since JDK 15.

Instead, we could use the Docker image for now. In the future, we need a different way, for example, use GraalVMs JavaScript.

@coderzpw1
Copy link
Author

Ok, I got it. Thank you for your answer.

@saig0
Copy link
Contributor

saig0 commented Aug 9, 2022

In case, someone is interested to migrate to GraalVM JS, here is a short guide: https://golb.hplar.ch/2020/04/java-javascript-engine.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants