Scenario: Bad logging configuration internal to war file. No Manager app in the instance.
Is there a JVM property or something we can set that will cause Tomcat to NOT redeploy on restart? That way we can just edit the properties file under webapps. Can't just temporarily move the war file for the startup as this would cause all kinds of organizational auditing problems.
This is a temporary fix, of course. I've been pushing Spring based external configuration for log4j to handle exactly this sort of thing.