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.
