Details
-
Task
-
Resolution: Done
-
Major
-
None
-
None
Description
There have been problems with the SecurityContext leaking into thread pools, due to the use of the InheritableThreadLocal.
Do we still need this to be an InheritableThreadLocal? If so, is there anything we can do to stop it from leaking into thread pools?
Attachments
Issue Links
- is related to
-
WFLY-485 Review SecurityContext associations
- Closed