Hi again! I'm happy to hear that. Cool!
I've just tried in my local environment and I didn't see it, but I probably didn't play enough. What I'm sure about is that I've seen the error on a production server also, like I mentioned in one of the previous comments, where I'm using pure catalina.sh to operate Tomee, so no NetBeans or any other tools. ________________________________ From: Romain Manni-Bucau [via OpenEJB] <[email protected]> To: zmirc <[email protected]> Sent: Saturday, September 28, 2013 1:07 PM Subject: Re: Memory leak by openejb.pool.scheduler Can you test starting/stopping tomee normally (without using manager app = not using netbeans) I think i idenyify the issue. Fyi manager app is not the default in tomee and this usage can get some cases not tested. I'll check your sample next week. Le 28 sept. 2013 11:32, "zmirc" <[hidden email]> a écrit : > 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. > ________________________________ If you reply to this email, your message will be added to the discussion below: http://openejb.979440.n4.nabble.com/Memory-leak-by-openejb-pool-scheduler-tp4665263p4665338.html To unsubscribe from Memory leak by openejb.pool.scheduler, click here. NAML -- View this message in context: http://openejb.979440.n4.nabble.com/Memory-leak-by-openejb-pool-scheduler-tp4665263p4665347.html Sent from the OpenEJB User mailing list archive at Nabble.com.
