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
While [Inheritable]ThreadLocals are relatively easy to start with to pass along request related information, ThreadLocals come with a non-negligible cost and maintenance burden:
TLs can cause very hard to detect memory leaks as objects (and classes!) are (often permanently) attached to a thread.
TLs and their usage are hard to test
(The use of) TLs can accidentally share data across requests
Use of TLs becomes complex and hard to reason about
The proper way of sharing request related information is to use CDI's @RequestScoped beans.
To Reproduce
No response
Actual Behavior
No response
Expected Behavior
No response
Additional context
No response
System information
No response
The text was updated successfully, but these errors were encountered:
Is this a possible security vulnerability?
Describe the bug
While
[Inheritable]ThreadLocal
s are relatively easy to start with to pass along request related information,ThreadLocal
s come with a non-negligible cost and maintenance burden:The proper way of sharing request related information is to use CDI's
@RequestScoped
beans.To Reproduce
No response
Actual Behavior
No response
Expected Behavior
No response
Additional context
No response
System information
No response
The text was updated successfully, but these errors were encountered: