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=6617>. 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=6617 Iterating over session attribute name enumeration fails with a ConcurrentModificationException on org.apache.catalina.util.Enumerator.nextElement(Enumerator.java:166); [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2002-10-29 00:02 ------- I've seen this exception as well under different circumstances that are definitely valid. Suppose that while enumerating through the session attributes, another request is made that accesses the same session and removes an attributes. Since the Session attributes are accessed by different threads and different requests, the use of the Enumerator is definitely valid. This can happen either during stress testing when multiple requests are performed for a single user with little time between or when a user opens multiple browsers and performs two concurrent requests. In either case, this is a vliad bug. The session attributes Collection should be cloned before an Enumerator is returned. -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
