Bug #14462
closed
when javascript engine timeout, we shutdown the thread before having a chance to report about it
Added by Nicolas CHARLES over 5 years ago.
Updated over 5 years ago.
Category:
Performance and scalability
Description
in JavascriptEngine, we have a timeout of 5 secondes, and when we timeout, we terminate the thread
it can cause
```Exception caught during policy update process: Task java.util.concurrent.FutureTask@4cc89444 rejected from java.util.concurrent.ThreadPoolExecutor@7a2cae84[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 24]``` but we are unsure
we need to add logging BEFORE shutown
- Target version changed from 4.3.11 to 4.3.12
I'm not sure it is that that cause the reported error. It seems that the JS engine is (at leat trying to) reporting on its errors. On the other hand, the reported error is the same as https://issues.rudder.io/issues/14465.
So perhaps the JS timeout because of some load, but it's the load which caused the exception. Still, it's useful to know that both problem are/were corelated, perhaps it is a way to reproduce the `Task java.util.concurrent.FutureTask rejected from java.util.concurrent.ThreadPoolExecutor` problem.
- Related to Bug #14465: Generation fails with "Task FutureTask rejected from ThreadPoolExecutor" due to timeout in JS computation added
- Subject changed from when javascript engine timeout, we shutdown the threa before having a chance to report about it to when javascript engine timeout, we shutdown the thread before having a chance to report about it
- Target version changed from 4.3.12 to 4.3.13
- Target version changed from 4.3.13 to 4.3.14
- Target version changed from 4.3.14 to 587
- Target version changed from 587 to 4.3.14
- Status changed from New to Rejected
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by