https://issues.apache.org/bugzilla/show_bug.cgi?id=49986
--- Comment #1 from Sebb <s...@apache.org> 2010-09-23 10:18:53 EDT --- Looks like a problem to me if the class can be called from multiple threads. If not, then why have any synch. blocks at all? Could perhaps be fixed by making reload volatile, but the reload variable can be set false elsewhere without synch. The servletClassLastModifiedTime also looks to be used in a similar way; that is a long so could potentially an invalid value could be read. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
