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=27249>. 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=27249 disposed ComponentLocator exception (when sitemap has timestamp in the future?) [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2004-05-26 20:52 ------- Fixed: - the sitemap modification checks now use equality (and no more greater than), meaning that reload always happens once even if the modification date is in the future. - when a sitemap is modified, the "old" processor is actually disposed only when all requests it currently processes (either separate thread or "cocoon:") are terminated. Pier, the ConcurrentModificationException you got should be a side effect of the request being processed still using the disposed CM, and should no more occur now. Please cross-check!
