On 2/28/07, Rachel Wilson <[EMAIL PROTECTED]> wrote:
>> It looks like you have bad syntax in you log4j.properties file. If that were the case, i would have expected it to fail the first time i started the application? to be clear, here are the steps to reproduce the error [1] deploy an unpacked webapp "myapp" to $TOMCAT_HOME/webapps/myapp [2] start tomcat [3] all webapps start and work fine, both tomcat and application logging works fine [4] using the /manager webapp stop myapp [5] myapp (seems to) shut down fine [6] using the /manager webapp start myapp [7] myapp does not start because of the reported error
Sorry, didn't realize this was happening on a reload. This problem is pretty common when restarting web applications. Libraries that use singletons etc. don't get reinitialized correctly when the web application is reloaded. These can be tough to track down, because more often than not, the issue is not in your code. Oddly enough I haven't seen this particular error coming out of log4j before... Once your library count gets higher, it becomes harder and harder to keep the applications reloading properly - more from memory leaks through the reload more than anything else. We gave up on it and restart tomcat. We run a cluster, so restarting just one version of tomcat has little effect on our system. Your log4j.properties looks OK to me. -- Gary Evesson
