Moreover, with the original project, the one where I discovered this Tomee's bug, by repeating this cycle more times (run,undeploy,deploy,redeploy etc...), Tomee can't be stopped anymore. The only solution is to kill the process. I didn't get this behavior with this small sample, but I just wanted to mention it again.
-- View this message in context: http://openejb.979440.n4.nabble.com/Memory-leak-by-openejb-pool-scheduler-tp4665263p4665337.html Sent from the OpenEJB User mailing list archive at Nabble.com.
