I'm using Rhino 1.6r2 through the javax.script
API. I know that the Rhino engine claims to be MULTITHREADED: "The engine implementation is internally thread-safe and scripts may execute concurrently although effects of script execution on one thread may be visible to scripts on other threads."
What I'd like to know is, under what exact conditions would the effects of one script execution be visible to another? In my code, I sometimes re-use a ScriptEngine
object, but for every execution I create a new SimpleBindings
and pass it to eval(String, Bindings)
. With this arrangement, is there any way that internal state could leak from one execution to another? If so, how?
There's a very informative answer here, but it doesn't quite tell me what I need to know.
Yes, JSR223 didn't specify how variables in script language should be bound with given
Bindings
. Therefore it is totally possible the implementers choose storing global scope variables in engine instance and reuse it even given differentBindings
when evaluating script.For example, JRuby's JSR223 binding has one mode working in this way
The javax.script package is thread-safe, but if your script isn't, you can have concurrency problems. The global variables inside the script is visible to all Threads. So, avoid using global variables inside your javascript functions
I'm running into this problem right now. My javascript is as follows:
And I'm running it inside a ThreadPool(4) 10.000 times, and printing the result.
This is a piece of the output:
I modified https://stackoverflow.com/a/1601465/22769 answer to show that rhino script engine execution is completeley thread safe if you specify the context in the eval() function. The sample calls fibonacci javascript function 100 times from 5 different threads concurrently: