Dariusz Łuksza wrote:
> Hi,
>
> If there aren't any additional request to Servlet-Service part of
> monitoring, I'll move to cache overview, or maybe there are some ? ;)
>
> I think that that part I'll divide to three or four smaller parts that
> would be easier to achieve. So first part would be getting list of
> configured caches and expose them on JMX with additional features like
> refresh and reload them. Next part would be getting list of used cache
> keys (I think that one would be the easiest ;)). After that I'll tray
> to add additional information to CacheKey that would gave possibility
> of dividing them in to separate nodes that would group them in to
> logically organized group eg. based on request url (that part would be
> the hardest I think ;)).
We could also group by usage. It's important to see if there are cache
entries that are either hardly or even never used.
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member [email protected]
________________________________________________________________________
