I don't think there is a general solution for this, but there are specific solutions for different runtime environments. We should provide some kind of hook to allow plugging in a solutions for a particular runtime environment.
On Mon, Jun 20, 2016 at 2:09 PM, Mikael Ståldal <[email protected]> wrote: > I have had the same issue for a long time, and it is a tricky one. > > It is the background for this ticket: > https://issues.apache.org/jira/browse/LOG4J2-1010 > > On Mon, Jun 20, 2016 at 9:36 AM, Greg Thomas <[email protected]> > wrote: > >> On 19 June 2016 at 23:25, Remko Popma <[email protected]> wrote: >> > By setting system property isThreadContextMapInheritable to true, the >> > ThreadContext map will be stored in a InheritableThreadLocal. >> >> Unfortunately not; firstly, it won't work with a ThreadPoolExecutor >> (which admittedly my example didn't use, but I did say it was >> contrived ;)) >> >> Greg >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > [image: MagineTV] > > *Mikael Ståldal* > Senior software developer > > *Magine TV* > [email protected] > Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com > > Privileged and/or Confidential Information may be contained in this > message. If you are not the addressee indicated in this message > (or responsible for delivery of the message to such a person), you may not > copy or deliver this message to anyone. In such case, > you should destroy this message and kindly notify the sender by reply > email. > -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* [email protected] Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
