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=5719>. 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=5719 deadlock in StandardContext reload ------- Additional Comments From [EMAIL PROTECTED] 2002-01-07 10:04 ------- I've managed to reproduce this by modifying the examples/forward/forward.jsp with 4.0.2 change the first jsp block to: <% this.getServletContext(); try {Thread.sleep(10000); } catch (Exception e) {}; this.getServletContext(); double freeMem = Runtime.getRuntime().freeMemory(); double totlMem = Runtime.getRuntime().totalMemory(); double percent = freeMem/totlMem; if (percent < 0.5) { %> now, access this jsp, and a couple of seconds after hitting it, make a reload request. The system deadlocks: because getServletContext is synchronized, and the reloading thread has hold of the locks it needs to complete.... d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
