DO NOT REPLY [Bug 10967] - Java Deadlock in WebappClassLoader

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10967>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10967

Java Deadlock in WebappClassLoader





------- Additional Comments From glenn@apache.org  2002-07-19 13:42 -------
I also ran into a similar situation with 4.1.7 but with jasper 1 instead of
jasper 2.  What seemed to trigger it was a JSP page recompile.  The thread
dump in my case looks like there was a deadlock trying to load the new
JSP servlet class.  The JSP recompile was done shortly after a manager reload.

I had 4 threads with the following state:

"Ajp13Processor[8009][125]" daemon prio=5 tid=0x5be8b0 nid=0xb7 waiting for
monitor entry [0xe93be000..0xe93c19e0]
        at java.lang.ClassLoader.checkCerts(ClassLoader.java:535)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:487)
        at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111)
        at
org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1650)

And 25 threads in this state:

"Ajp13Processor[8009][117]" daemon prio=5 tid=0x69ab98 nid=0xaf waiting for
monitor entry [0xe953f000..0xe95419e0]
        at java.lang.Class.newInstance0(Native Method)
        at java.lang.Class.newInstance(Class.java:237)
        at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.load(JspServlet.java:138)

Then the customer did another reload when he didn't see his JSP recompile
complete.  And I ended up with everything locked because the reload was waiting
for the above deadlocks.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>