We have a grails app that is being tested on tomcat 6.
We have a META-INF/context.xml defined in our WAR file. We start tomcat and deploy this WAR via the manager interface to the root context. The WAR is deployed OK and the app runs great. We then go into the tomcat manager and do a "STOP" on the context.
Noticed this output in the tomcat STDOUT
log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository.
Secondly, we then do a tomcat "undeploy" which deletes all the deployed context files. When this is completed, the following Grails jars are left in the <contextRoot>/WEB-INF/lib directory. Because of this you cannot re-deploy your WAR again unless you kill the entire tomcat process to delete the jars. Maybe something in grails' ServletContextListener is not properly handling a shutdown and releasing resources?