Hi,
I guess that this is generated because
tomcat has seen that your jsp file has
been updated (its timestamp is newer
than the generated .class file), and so
is trying to move the class file generated
from the old .jsp file out of the way so
it can generate a .class file for the newer
version
I don't believe I changed the .jsp before getting the error. Is the
timestamp the only reason the .class would be regenerated?
I have many gigs free and liberal directory permissions. Maybe another
connection in my pool is using the old .class so it can't be overwritten?
Thanks,
-alex
On
