Hi!! Agreed with Justin about not being a real issue.. Check the last comment here: https://github.com/netty/netty/issues/2522 You could try to put a FastThreadLocal.destroy() on the application exit. Anyway, there are good chances that the memory leak protection (https://wiki.apache.org/tomcat/MemoryLeakProtection) of Tomcat will recognize it as a memory leak because you'll need a complete GC cycle to get rid of the thead local instances.
-- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-Memory-leak-while-shutting-down-the-tomcat-server-with-embedded-JMS-server-tp4722906p4722963.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
