Lars Rottmann wrote: > > >>Lars Rottmann wrote: > >> Replacing the BucketMap with another Map implementation solves the > >> problem of Cocoon failing at high load (where the ECM fails to look up > >> a Selector, not the Selector looking up a handler). It does not cure > >> the warning message above. > > >Where do you replace the BucketMap with a Map? In the ECM? > >Did you try to do this replacement in the ExcaliburComponentSelector as > well? > > I did replace every occurence of StaticBucketMap in the > Excalibur-Component > package with a Hashtable. > Ah, ok - so, it seems that the BucketMap has threading problems. Replacing it with a HashMap solved the problem in the ECM. But replacing the BucketMap in the ECMSelector doesn't solve the other problem, as you still get the message. So, there must be another problem :) I know this is obvious, but I just wanted to restate it. I think we can assume that the HashMap has no threading problems.
So, has anyone a clue? Can it be the toString() method on your operating system? Hmm, I don't know. Carsten
