Thanks for the info. We haven't had the problem again so far, so we will leave it as is (the deadlock can should occur after a restart, so we can monitor it) I may look into the fix on my development pc and let you know.
Glen. 2007/2/21, Remy Maucherat <[EMAIL PROTECTED]>:
Glen Vermeylen wrote: > Hello all, > > We've seen strange behaviour on production (tomcat 5.5.20/java 6): > immediately after restart no-one could login. Using jconsole we saw that > there was a deadlock in the classloader. > Today I've also had the problem on development (tomcat 6.0.9/ java 6). > Its a > shame I was using tomcat 6.0.9 instead of 5.5.20, but it seems the two > problems are the same. > The problem occurs sometimes when multiple browsers are trying to > connect to > the server while it is still starting up. > I've tried to reproduce the problem on both 5.5.20 and 6.0.9 by trying to > start multiple browsers during application startup, but I cannot trigger > the > deadlock again. > Using jconsole I saw there were 2 httpthreads locking eachother. > > Below are the stacktraces of both threads (I also have screenshots of > jconsole showing the threads the deadlocks-screen). > > I couldn't find the problem myself, so I turn to this list for help. Please test the patch if you can. Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
