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?
> > You can deal with the warning by adding a 'pool-max="512"' to the > <map:pipes> section of the sitemap. But I fear this is just a workaround, > too. > Yes, I guess so. Carsten
