Lars Rottmann wrote: > 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.
Carsten
