Le 25 mai 04, à 10:49, Pier Fumagalli a écrit :...Two problems... Definitely, under load, Excalibur fails disposing/releasing components, and somehow, Cocoon keeps state EVEN between hard restarts of the JVM...
Anyone ever saw something like this?
Might be related to this very mysterious bug
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27249
which I've seen from time to time in all versions since cocoon-2.1rc2-dev (at least).
My comment of 2004-02-27 10:23 in the bug gives a reproducible case.
Yep, seems to be the same bug... And it's happening _A_LOT_ on our production environment :-( :-(
Have you noticed, by any chance, a ConcurrentModificationException somewhere in your tests?
I noticed that the ExcaliburComponentManager doesn't correctly synchronize on its m_componentHandlers hashmap, and that might be the root of our problems...
IIRC, hard restarts didn't help either in this case, the only "fix" was to edit the sitemap (add a space somewhere for example).
How come we're keeping state on the sitemap? Where?
Pier
smime.p7s
Description: S/MIME cryptographic signature
