DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=41661>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41661 Summary: JspConfig.init() is not synchronized Product: Tomcat 5 Version: 5.5.20 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] The 'JspConfig.init()' method can be called simultaneously from multiple threads at the same time, but it is not synchronized, so the initialization code in the body can be executed simultaneously by multiple threads. This can lead to a 'jsp-property-group' configuration being added twice to the 'jspProperties' vector. The symptom we noticed was that on some runs, the contents of the 'include-prelude' and 'include-coda' elements would be included twice in all compiled jsp files. This bug is hard to reproduce because it requires a run where the first thing that happens is that multiple jsp files are requested simultaneously. However, after adding a field containing a synchronization object and synchronizing on it across the if (!initialized) { ... } block, we haven't seen the problem reoccur. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
