All, There is an issue in Tomcat 5.0.x and 5.5.x which affects concurrency. The deal is HttpSession.getAttribute is not synchronized and can cause the failure of session variable lookup as well as an infinite or very long running loop to occur during a getAttribute call. There is no guarentee that setAttribute will remain synchronized in the future according the information from Tomcat developers in the original bug report and how this is always the developers problem. The Tomcat source code has different places where HttpSession.getAttribute and setAttribute are called (notibly the standard JSP tags jsp:getAttribute and jsp:useBean) which are not being synchronized when they need to be. These need to be found and reported as bugs so they can be corrected. Remember that access to the session in any way where the end developer (JSP or Servlet developers) can't synchronize and protect against concurrency issues or where it doesn't make sense for them to (JSP tags) needs to be found and reported as bugs. Any help is appreciated and it helps everybody. Everyone can send me their findings to mail alias [EMAIL PROTECTED] and I can be a point for creating the bug report in BugZilla for these particular bugs.
Please see: http://issues.apache.org/bugzilla/show_bug.cgi?id=36541 and http://issues.apache.org/bugzilla/show_bug.cgi?id=36586 for more details Thanks, Wade --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
