cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27249] - disposed ComponentLocator exception (when sitemap has timestamp in the future?)
Date Tue, 25 May 2004 12:34:49 GMT
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?)

bdelacretaz@codeconsult.ch changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|You cannot lookup components|disposed ComponentLocator
                   |on a disposed               |exception (when sitemap has
                   |ComponentLocator exception  |timestamp in the future?)



------- Additional Comments From bdelacretaz@codeconsult.ch  2004-05-25 12:34 -------
As hinted by Vadim, setting a subsitemap's timestamp reproduces the problem (or
a similar one).

Scenario:
1. Cocoon runs, load a page served by a subsitemap
2. touch -t 201012010000 sitemap.xmap (on the subsitemap)
3. reload the page
4. ComponentLocator exception happens (stack trace follows, trace1.txt)

5. Stop Cocoon
6. Delete /tmp/Jetty__*
7. Restart Cocoon, reload same page
8. ComponentLocator exception happens (stack trace follows, trace2.txt)

9. touch sitemap.txt (on the subsitemap)
10. Refresh page -> no more error

Setting the sitemap timestamp in the future causes the problem, which persists
after Cocoon restarts.

Resetting the timestamp to a correct one gets things back to a sane state.

Mime
View raw message