-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
The RuntimeExpressionResolver is holding the lock on the collection for the entire resolution of the expression step, this means there is a risk of deadlock across multiple threads
We need to double check but from our discussions we feel it was likely this locking was to protect the iterator from modifications to the underlying collection but we can handle that in a different way, the individual extensions are responsible for their own locking requirements.
- is cloned by
-
JBEAP-28893 [8.1] Revisit the locking in RuntimeExpressionResolver due to deadlock risk.
-
- Open
-