What is the Java Equivalent of C# "Logical Call Context"

Question

In .net, there is an "uber" thread-local-storage (TLS) which allows arbitrary TLS data to auto-magically "jump" from one thread to another. It is based on the CallContext class.

In other words, a logical request can spawn a hierarchy of new threads - and each of those threads will have access to the same TLS of the original thread. It is a very powerful feature, particularly for logging, authorization, multi-tenancy, or branding concerns.

What is the equivalent in Java?

Only in .net 4.5 has the "logical callcontext" gained a "copy on write" capability that allows threads to make private modifications to the logical callcontext. In other words, .net is still maturing this capability and providing greater stability.

If Java has an equivalent notion, how stable is it? What issues does it have?

Clarification

I already know that Java has a thread local storage (TLS) capability. That is not the question. I am asking if Java has an equivalent of the .net "logical call context" which is a much more powerful construct than simple TLS.

Answer 1

Maybe InheritableThreadLocal is what you're looking for?

I'm not sure if it's exactly the same, but as far as I understand it meets this requirement:

a logical request can spawn a hierarchy of new threads - and each of those threads will have access to the same TLS of the original thread.

From the docs

This class extends ThreadLocal to provide inheritance of values from parent thread to child thread: when a child thread is created, the child receives initial values for all inheritable thread-local variables for which the parent has values. Normally the child's values will be identical to the parent's; however, the child's value can be made an arbitrary function of the parent's by overriding the childValue method in this class. Inheritable thread-local variables are used in preference to ordinary thread-local variables when the per-thread-attribute being maintained in the variable (e.g., User ID, Transaction ID) must be automatically transmitted to any child threads that are created.

I don't know about the "copy on write" capability you mentioned, but I guess you can override InheritableThreadLocal.childValue(T) to proxy the parent's value so that writes don't go through to the parent and modify the current thread's local storage