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
Found by Oleg. When the StandardEvaluationContext was modified from an eager to lazy initialization model, this created an issue with two threads simultaneously triggering the lazy initialization. In initialization of the method resolvers it is possible for one thread to trigger initialization but during that initialization another thread grabs an 'empty list' of method resolvers (because the first thread has only created the list, not populated it yet).
Although only found for method resolvers this probably affects initialization of other pieces, they will be checked as part of fixing this issue.
Andy Clement opened SPR-7343 and commented
Found by Oleg. When the StandardEvaluationContext was modified from an eager to lazy initialization model, this created an issue with two threads simultaneously triggering the lazy initialization. In initialization of the method resolvers it is possible for one thread to trigger initialization but during that initialization another thread grabs an 'empty list' of method resolvers (because the first thread has only created the list, not populated it yet).
Although only found for method resolvers this probably affects initialization of other pieces, they will be checked as part of fixing this issue.
Affects: 3.0.3
Referenced from: commits 88560fd
The text was updated successfully, but these errors were encountered: