You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I assumed that using async.gracefulshutdown=false will kill all running threads properly, so that my application is not exposed to any memory leak problems. When I redeploy my application Tomcat is reporting that ThreadLocal connected to Sentry failed to be removed:
19-Jun-2017 22:06:57.423 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [io.sentry.context.ThreadLocalContextManager$1] (value [io.sentry.context.ThreadLocalContextManager$1@5d7c6e1d]) and a value of type [io.sentry.context.Context] (value [io.sentry.context.Context@40c92b58]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
Is there something that could be done in reference to above issue?
The text was updated successfully, but these errors were encountered:
Thanks for the report, I'll check this out ASAP. I haven't done a lot of testing with full blown application servers, I think this should hopefully be a quick fix tomorrow.
I'm using Tomcat 8 and lastest version of Sentry SDK:
I configured my logging in files:
log4j2.properties
sentry.properties
I assumed that using async.gracefulshutdown=false will kill all running threads properly, so that my application is not exposed to any memory leak problems. When I redeploy my application Tomcat is reporting that ThreadLocal connected to Sentry failed to be removed:
Is there something that could be done in reference to above issue?
The text was updated successfully, but these errors were encountered: