On 8 April 2010 07:47, Shahnaz Ali <shaan20...@gmail.com> wrote: > No, there was no any hot deployment.
But the evidence points to a change of class so something equivalent to a redeployment must have happened. Something caused a deployed class to be reloaded and that operation failed due to a class incompatibility. That is what happened. Unless the logs are somehow fabricated :) The cause of the crash however could be anything! Have a try at repeating it by dropping newer Wars and Jars. Upgrade your Java runtime to apply all the officially available fixes. Quit running Tomcat as root :) Regards, Michael Erskine. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
