Java ThreadLocal static?

As per the definition of ThreadLocal class

This class provides thread-local variables. These variables differ from their normal counterparts in that each thread that accesses one (via its get or set method) has its own, independently initialized copy of the variable. ThreadLocal instances are typically private static fields in classes that wish to associate state with a thread (e.g., a user ID or Transaction ID).

That means say 2 threads t1 & t2 executes someBMethod() and they end up setting x1 & x2(Instances of X) respectively. Now when t1 comes and executes someCMethod() it gets x1 (which is set by itself earlier) and t2 gets x2.

In other words, its safe to have a single static instance of ThreadLocal, because internally it does something like this when you invoke set

set(currentThread, value) //setting value against that particular thread

and when you invoke get

get(currentThread) //getting value for the thread

I study the java source code,

1. java.lang.Thread Class contains a instance variable as below.

   ThreadLocal.ThreadLocalMap threadLocals = null;

Because threadLocals variable is non-static, Every thread in a application (i.e., every instance of Thread Class) will have it's own copy of threadLocals map.

2. Key for this map is, current ThreadLocal instance, and value is the value which you pass as argument to ThreadLocal.set().

3. When you try to fetch value as ThreadLocal.get() , internally, it will fetch from the ThreadLocalMap of Current Thread.

In simple terms, you are getting & setting values from/to your current Thread Object, not from/to your ThreadLocal object.

Multiple threads executing B's someBMethod, will end up updating the SAME A's static ThreadLocal variable myThreadLocal

Yes, they operate on the same object. However, it is important to realize that the way ThreadLocal works is that each thread has its own, separate value. Thus if you have ten threads writing to myThreadLocal and then reading from myThreadLocal, each will see the correct (i.e. their own) value.

To put it another way, it does not matter which class or object writes to an instance of ThreadLocal. What matters is the thread in whose context the operation is performed.