If you know exactly what ThreadLocal causes a leak, you can try to just clean it with reflection at the end of your Callable.
Sergi 2017-03-15 10:10 GMT+03:00 Isaeed Mohanna <[email protected]>: > Hi > As i have mentioned before its not me that is using the ThreadLocal but a > 3rd party library that i am using is doing so. I am trying to get them to > fix it but until they do so i wanted to verify if I can remedy the > situation without having to wait for them. > ill push them to change their implementation. > Thanks alot > > On Tue, Mar 14, 2017 at 8:59 PM, vkulichenko < > [email protected]> wrote: > >> Isaeed, >> >> There is no such way. >> >> If you're using thread local, you should properly clean it when the value >> is >> not needed anymore. Another way it to use something else instead. >> >> Why are you using thread locals in compute in the first place? What is the >> use case for this? >> >> -Val >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/IgniteThread-ThreadLocal-Memory-Leak-tp11168p11171.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >
