InheritableThreadLocal values are unexpectedly shared across threads when enabling access-log in EAP undertow

Issue

• Our application sets InheritableThreadLocals in its HTTP request processing. When we enable EAP's access-log in the undertow subsystem, we begin to see issues as the InheritableThreadLocals values are shared across threads and requests or a request's InheritableThreadLocal value is cleared unexpectedly by another to cause NullPointerExceptions.