DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-04-15 08:43 --- I'm experiencing the problem, too (cocoon 2.1.4). In my setup, it has certainly nothing to do with CVS (though the sitemap has a CVS Id). I have an EAR that deploys fine using JBoss-3.2.3 on several machines (both Windows and Linux types). There is one machine, however, where everything is -- to the best of my knowledge -- configured in the same way as on all the other machines, and there I get the error. Adding e.g. a space to the sitemap helps only temporarily. The applictaion uses the sitemap to generate a frameset and each frame then uses the sitemap to get its contents. The frameset is always generated, the frames aren't. When I add the space to the sitemap, I can reload one frame. The second fails again (quite a tedious way to get your GUI ;-) ).
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-04-15 09:21 --- Just guessing, could it be that this is related to the delayed checking of the sitemap? The DelayedRefreshSourceWrapper is used and if you do a CVS commit this takes more time perhaps than editing the file by hand? If you can reproduce the problem, you could try it by removing DelayedRefreshSourceWrapper from the DefaultTreeBuilder and use the Source directly. (PS: The delay time is 1 sec, so if everything is ok, this can't be the reason, but who knows?)
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception [EMAIL PROTECTED] changed: What|Removed |Added Version|2.1.3 |Current CVS 2.0 --- Additional Comments From [EMAIL PROTECTED] 2004-02-28 11:21 --- I've been able to reproduce the problem with the current CVS version. Did not happen when committing a minimal sitemap (request generator + xml serializer), I had to take the exact same application tree that ran under cocoon-2.1rc2-dev in my app. Here's the scenario, I'll attach the logs if someone wants to analyze them: 1. empty all logs, set all logs to DEBUG 2. start Cocoon, make a request (with pass1=true so it can be found in the logs), request processed ok 3. make some change to the sitemap (in XML comments) 4. request with pass2=true, ok 5. commit sitemap changes to my CVS 6. request with pass3=true, get disposed ComponentLocator exception 7. add one space to sitemap after ?xml...? to cause it to reload 8. request with pass4=true, ok So the problem exists in the current CVS. It's no big deal as such but probably hides something else.
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-28 11:22 --- Created an attachment (id=10604) Complete DEBUG logs of the above scenario
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-28 11:24 --- Note also that when the problem happens it persists after a restart of Cocoon, even if I delete /tmp/Jetty____/. Only editing the sitemap makes it go away. I'm doing all these tests with Jetty, ./cocoon.sh servlet, macosx, JDK 1.4.1
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-28 11:30 --- Next attachment is a smaller log, where just one request after startup causes the problem (which was present before stopping Cocoon). /tmp/Jetty____/ was deleted before restart. Should be the smallest set of log messages where the problem happens.
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-28 11:31 --- Created an attachment (id=10605) smaller DEBUG log, where error happens on first request after restart
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-28 12:48 --- Bertrand, 1 Did you really mean to change to current _2.0_ for this bug? 2 Are you using eclipse (for cvs commit)? Geoff
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception [EMAIL PROTECTED] changed: What|Removed |Added Version|Current CVS 2.0 |Current CVS 2.1 --- Additional Comments From [EMAIL PROTECTED] 2004-02-28 13:20 --- 1 Did you really mean to change to current _2.0_ for this bug? Sorry no, fixed it 2 Are you using eclipse (for cvs commit)? No, command-line CVS. But I haven't been able to reproduce the problem with simple sitemaps, for now I only see it in my application. In the meantime I have added log messages to the CocoonComponentManager, which show the problem: IIUC the sitemap component manager is disposed, and later on AbstractEnvironment calls lookup() on this disposed manager, causing the ExcaliburComponentManager to complain. The attached logs show the problem, search for CocoonComponentManager.dispose in sitemap.log (next attachment log with additional CCM messages) I don't know enough about CocoonComponentManager to go further - either it is disposed at the wrong time, or its sourceResolver should not be set to null in dispose(). The relation to the CVS commit is still a mystery though, but the above failure scenario with CVS works every time here ;-)
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-28 13:22 --- Created an attachment (id=10606) Logs with additional CCM messages, show the dispose() problem
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-27 10:23 --- I've had the problem again on an existing cocoon-2.1rc2-dev installation (compiled on August 8 2003), scenario: 1. Cocoon is running fine 2. Do a CVS commit, causes sitemap.xmap to change (but only XML comments change, due to the CVS log being written there) 3. Next request which uses the sitemap in question gives the error 4. After adding a space somewhere in the sitemap to cause it to reload, back to normal. Interesting part of the stack trace: java.lang.IllegalStateException: You cannot lookup components on a disposed ComponentLocator at org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:199) at org.apache.cocoon.components.CocoonComponentManager.lookup(CocoonComponentManager.java:315) at org.apache.cocoon.components.source.SourceUtil.toSAX(SourceUtil.java:165) at org.apache.cocoon.components.source.SourceUtil.toSAX(SourceUtil.java:126) at org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.build(DefaultTreeBuilder.java:388) Line 165 in SourceUtil is: xmlizer = (XMLizer) manager.lookup( XMLizer.ROLE); so apparently the manager is not in the expected state when this happens. I don't have the CVS version number of this SourceUtil handy but it was obtained with a cvs export -d 2004-08-08.
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-27 10:34 --- The failure scenario below is repeatable on my cocoon-2.1rc2-dev installation: 1. Make some change to sitemap 2. cvs commit of the sitemap (to my own CVS), wait for commit to be finished 3. reload page - gives the above exception Haven't been able to reproduce it without doing the commit, I tried various renaming and copying scenarios on sitemap.xmap but didn't see the problem. Maybe looking at what CVS does to the file during the commit would help.
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-27 10:37 --- Could not be much more than a touch without changing anything, a comment with $ID$ could be changed. Is it reproducable with a simple touch?
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-27 10:55 --- I can confirm the behavior exactly as Bertrand reports; a simple touch doesn't cause the bug to happen. This is on Cocoon 2.1.3 with Tomcat 4.1.12-jdk14.
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-27 10:58 --- Additional info: as you may suspect, if the CVS id comment is removed from the sitemap, the bug doesn't happen. So this seems to be solely related to the parsing of the XML comment containing the CVS version info.
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-27 13:52 --- So this seems to be solely related to the parsing of the XML comment containing the CVS version info. hmm..if you remove the $Id$ keyword, CVS won't do any change to the file when doing the commit, so the problem is not necessarily related to the comments. I was more thinking of the way used by CVS to update the file (some sequence of file open / write / close / file date change) which causes Cocoon's file change detection to do something funny. It might be interesting to look at the debug messages related to how the sitemap.xmap change is detected by Cocoon.
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-27 14:42 --- But after removing the $Id$ keyword the exception no longer occurs after a CVS commit. What should I be looking for in the sitemap debug log?
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-27 16:26 --- What we're looking for is the difference between a) a CVS commit when sitemap contains $Id$, which causes the problem and b) a modification of the sitemap with an editor, which is ok In terms of the detection and processing of the changed sitemap. So I'd first activate all debug logs and look for messages related to b), then run scenario a) and see if the logs indicate a different processing sequence or give a hint as to what might go wrong. If you want to dig further, you might want to ask on cocoon-dev which classes are involved in the detection of sitemap changes, to know where to look. I don't know this part of the code well.
DO NOT REPLY [Bug 27249] - You cannot lookup components on a disposed ComponentLocator exception
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=27249. 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=27249 You cannot lookup components on a disposed ComponentLocator exception --- Additional Comments From [EMAIL PROTECTED] 2004-02-26 15:13 --- Also from Christian Mayrhuber [EMAIL PROTECTED] on users@: I had this issue too, both in 2.1.3 and 2.1.4. I've the impression that this issue has something to do with sitemap reloading. The only hack I found was to disable the Disposable interface in ExcaliburComponentManager.
