[EMAIL PROTECTED] wrote:
>
> Hello,
>
> two days ago, I posted the attached mail to the cocoon-dev-list.
> After further investigations I learned that the Avalon-list would
> be a better place to start, there I go...
>
> <snip>
>
> Hello,
>
> is there an official way to get the pool-states at runtime ?
Funny you should mention that... We are working on instrumenting Excalibur
now. The stuff we are working on is in scratchpad, and hopefully will
make it out soon.
> In the development-process I use a modified version (ugly hack) of the
> DefaultPool to check weather there are unsolved pooling-problems (sizing
> problems, recycling-problems, etc.). I use a small routine to ask all
> DefaultPool-
> Instances about their min-, max-, ready-, active-state and dump the
> data e.g. to STDOUT.
> In the future I can think of a generator which collects the data and a
> stylesheet
> which transforms the data to SVG for visual monitoring ;^)
Let's wait until the instrumenting is done. You will find that the
solution we provide is very elegant, and allows specific runtime classes
to gain access to the runtime state of some of the Components (like pooling).
>
> (See attached file: DefaultPool.java)
> If there are official ways to monitor the C2-Pool-State I would prefer
> to use the official 'interfaces', but until now I do not know them...
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
