I'm happy that you fixed that bug. Thank you! I'm under huge pressure because of a very random and not reproducible bug, therefore I have to post-pone a little bit isolating the leaking error into a sample project. I would really appreciate if someone could help. I'm desperate because of it. The whole project is screwed because of it. This is: http://stackoverflow.com/questions/18992241/random-jsf-error-no-saved-view-state-could-be-found/18999855 <http://stackoverflow.com/questions/18992241/random-jsf-error-no-saved-view-state-could-be-found/18999855> There is a very long discussion happening there, but without luck until now. Any help would be priceless.
-- View this message in context: http://openejb.979440.n4.nabble.com/Memory-leak-by-openejb-pool-scheduler-tp4665263p4665296.html Sent from the OpenEJB User mailing list archive at Nabble.com.
