Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
PrimeApplicationContext is not thread safe
See original GitHub issue1) Environment
- PrimeFaces version:
7.0.RC3 - Does it work on the newest released PrimeFaces version? No
- Does it work on the newest sources in GitHub? No
2) Explanation
The PrimeApplicationContext is an application scoped object that is lazily initialized. However, its initialization is not protected by any synchronized blocks or other thread safety code. So if X threads call PrimeApplicationContext.getCurrentInstance(facesContext) at the same time, they may instantiate as many as X PrimeApplicationContext instances.
Another aspect of PrimeApplicationContext that isn’t thread safe is the lazy initialization of member data (such as VirusScanner). This article explains the issue in detail, but essentially the current implementation may allow threads to access partially initialized objects.
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
done! @stiemannkj1 @melloware @cnsgithub @jxmai @Rapster it would be great if you could give my changes a try in your applications, if everything works as expected before we release the final.
@tandraschko just ran all the Faces tests and everything is working great!