I understood the issue but not the steps to reproduce it (where should i download the "big project" typically).
That said if you can build tomee from sources and test again I hope my fix helped *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/10/2 zmirc <m_chi...@yahoo.com> > Hi! > > Sorry, but I didn't actually understand what your message was in the last > reply. > Did my report helped somehow and you've added a new fix or...? > > Regarding the second part, the following: > > One more strange thing: > > 1. Deploy the big project, the one with many @Schedule. > > 2. Undeploy it. > > 3. Deploy the sample project used for reproducing the @Schedule leak > bug. > > During deployment, errors appear for @Schedule of the big project. This > > shouldn't happen because that project was undeployed before. > > > I will try to say it again. Basically, I deploy a project which has some > @Schedule methods. I undeploy it, then I deploy a completely other project. > During deployment of the latest one, the @Schedule from the first project > throw errors exactly how it happens in the first part of my last reply, > when I was redeploying the same project. > > 2.1. During redeployment, all @Schedule executions crash once, which > > generates a huge amount of logs. That's something new that happens. They > > shouldn't start if deployment is not done...or...whatever other > protection, > > because the current situation is not so desired. > My question about the above is: why do those logs appear for @Schedule > methods that shouldn't exist anymore in Tomee, because that project was > undeployed before the new one was deployed. > > Thank you for such a nice and fast support! > > > ________________________________ > From: Romain Manni-Bucau [via OpenEJB] < > ml-node+s979440n4665387...@n4.nabble.com> > To: zmirc <m_chi...@yahoo.com> > Sent: Wednesday, October 2, 2013 10:31 AM > Subject: Re: Memory leak by openejb.pool.scheduler > > > > Hmm > > Not sure I got the "big project" side of your answer but I hacked it a bit > (in particular the restart step which was something I never understood how > it could work and you prooved it was not working ;). > > > > *Romain Manni-Bucau* > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > *Blog: **http://rmannibucau.wordpress.com/*< > http://rmannibucau.wordpress.com/> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* > > > > 2013/10/1 zmirc <[hidden email]> > > > > Hi! > > > > I'm back with feedback for 1.6.0 2013.10.01. > > 1. I don't see the leak log anymore. > > 2. @Schedule seems to be properly working after restart. > > 2.1. During redeployment, all @Schedule executions crash once, which > > generates a huge amount of logs. That's something new that happens. They > > shouldn't start if deployment is not done...or...whatever other > protection, > > because the current situation is not so desired. > > > > /// I have attached the complete logs generated at a redeployment > > redeploy-log.txt > > <http://openejb.979440.n4.nabble.com/file/n4665382/redeploy-log.txt> > > > > One more strange thing: > > 1. Deploy the big project, the one with many @Schedule. > > 2. Undeploy it. > > 3. Deploy the sample project used for reproducing the @Schedule leak bug. > > During deployment, errors appear for @Schedule of the big project. This > > shouldn't happen because that project was undeployed before. > > > > > > > > -- > > View this message in context: > > > http://openejb.979440.n4.nabble.com/Memory-leak-by-openejb-pool-scheduler-tp4665263p4665382.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-tp4665263p4665387.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-tp4665263p4665388.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
