This TechNote provides a link to the JRun4 Updater 6 hot fix JAR file that contains the fix for the following JRun defect:
JRun synchronizes the session object internally. JRun goes into deadlock mode as the application is trying to synchronize the session again.
The JVM will deadlock due to the above bug and the following stack can be seen in the thread dump.
Found one Java-level deadlock: ============================= "web-51": waiting to lock monitor 0x00abb90c (object 0x35ec3f48, a jrun.servlet.session.JRunSession), which is held by "web-31" "web-31": waiting to lock monitor 0x00abba4c (object 0x27b24d78, a jrun.servlet.session.SessionService), which is held by "web-51" Java stack information for the threads listed above: =================================================== "web-51": at jrun.servlet.session.JRunSession.updateLastAccessTime(JRunSession.java:370) - waiting to lock <0x35ec3f48> (a jrun.servlet.session.JRunSession) at jrun.servlet.session.SessionService.getCookieSessionID(SessionService.java:1103) - locked <0x27b24d78> (a jrun.servlet.session.SessionService) at jrun.servlet.ForwardRequest.getRequestedSessionId(ForwardRequest.java:415) at jrun.servlet.ForwardRequest.isRequestedSessionIdValid(ForwardRequest.java:455) at jrun.servlet.ForwardRequest.getSession(ForwardRequest.java:332) at jrun.servlet.ForwardRequest.getSession(ForwardRequest.java:308) ...... "web-31": at jrun.servlet.session.SessionService.getCookieSessionID(SessionService.java:1099) - waiting to lock <0x27b24d78> (a jrun.servlet.session.SessionService) at jrun.servlet.ForwardRequest.getRequestedSessionId(ForwardRequest.java:415) at jrun.servlet.ForwardRequest.isRequestedSessionIdValid(ForwardRequest.java:455) at jrun.servlet.ForwardRequest.getSession(ForwardRequest.java:332) at jrun.jsp.runtime.JRunPageContext.initialize(JRunPageContext.java:83) at jrun.jsp.runtime.JRunJspFactory.getPageContext(JRunJspFactory.java:67) .... Found 1 deadlock.
Note: Macromedia strongly recommends installing and testing hot fixes in your test/staging environment prior to deployment on live production systems.
JRun engineering has fixed the JRun deadlock issue with the hot fix provided below. Follow the instructions to install the hot fix :
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.
