Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
4.2.0, 5.0.0, 2.26.30, 3.2.7, 4.1.2
-
None
-
None
-
3
-
Tiger
-
Tiger Sprint 151, Tiger Sprint 152
Description
The WhitelistedClassesResourceGuard class is not thread-safe, yet a single instance of it is used by Wicket in (possibly) multiple concurrent threads.
As a result, access to resources may occasionally be denied because the list of whitelisted prefixes is not properly initialized yet. One example we've seen is a failing call for the background image of the console application.
Attachments
Issue Links
- causes
-
CMS-10671 Use double checked locking pattern for lazy initialization of the WhitelistedClassesResourceGuard singleton
- Closed
- is backported by
-
CMS-10649 [BACKPORT 10.2] WhitelistedClassesResourceGuard is not thread-safe
- Closed
-
CMS-10650 [BACKPORT 7.9] WhitelistedClassesResourceGuard is not thread-safe
- Closed
-
CMS-10651 [BACKPORT 11.1] WhitelistedClassesResourceGuard is not thread-safe
- Closed
-
CMS-10652 [BACKPORT 11.2] WhitelistedClassesResourceGuard is not thread-safe
- Closed