You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys,
We use delight-nashorn-sandbox for evaluating js code in Java container application, we recently had a problem with Executor thread not set after 100 ms in any code.
I was able to replicate the problem in debug mode set to threadMonitor to null,
I'm instantiating the NashornSandboxImpl and creating a spring bean to improve performance and to use just insert the context in the ScriptContext, the application went through stress tests and withstood well, but on a usual day and without much use there was this problem.
I managed to work around the problem by resetting the nashorn instance if there is an IllegalStateException.
Thank you for your attention.
The text was updated successfully, but these errors were encountered:
Maybe there could be some issues with concurrent threads being run by the JVM. What have you configured as maxCPUTime (assuming 100ms)? Would it be possible to increase that to lets say 1000 ms and see if the issue persist?
Hi guys,
We use delight-nashorn-sandbox for evaluating js code in Java container application, we recently had a problem with Executor thread not set after 100 ms in any code.
I was able to replicate the problem in debug mode set to threadMonitor to null,
I'm instantiating the NashornSandboxImpl and creating a spring bean to improve performance and to use just insert the context in the ScriptContext, the application went through stress tests and withstood well, but on a usual day and without much use there was this problem.
I managed to work around the problem by resetting the nashorn instance if there is an IllegalStateException.
Thank you for your attention.
The text was updated successfully, but these errors were encountered: