Hi Carsten, >> This showed to me that my guess was obviously right. The log messages >> I posted earlier raised the suspicion in me that maybe the >> StaticBucketMap used by the excalibur-component package isn't really >> threadsafe. So I patched the ExcaliburComponentManager and >> ExcaliburComponentSelector and replaced all references to it with a >> java.util.Hashtable. Okay, I know this is not the fastest solution, >> but it worked. The "ComponentLocator exception >> from parent CM during lookup" appeared no longer in the logs. So >> I fear I've >> found a serious bug there. >> >Cocoon currently uses commons-collections-2.1, did you try the latest version from CVS. There were some bug fixes to the StaticBucketMap >(which is now in the map subpackage). I don't know if the bug fixes are fixing threading problems, but perhaps it's worth a try.
I worked with the version shipped with Cocoon as well as the latest CVS version from today (the new one from the map subpackage). The effect is the same. The ECM looks up a null reference and reinitializes it's component mappings with an empty configuration. From then on Cocoon only delivers error messages to the client. Lars Vodafone Global Content Services Limited Registered Office: Vodafone House, The Connection, Newbury, Berkshire RG14 2FN Registered in England No. 4064873 This e-mail is for the addressee(s) only. If you are not an addressee, you must not distribute, disclose, copy, use or rely on this e-mail or its contents, and you must immediately notify the sender and delete this e-mail and all copies from your system. Any unauthorised use may be unlawful. The information contained in this e-mail is confidential and may also be legally privileged.
