> Just upload it to JIRA anyway IMO. They can always reject > it, and at least > then it's freely available for anyone who might find it > interesting even if > it never makes it into the official source. > > Hmm.. StatusGenerator. That reminds me, I keep meaning to > get around to > adding some information to that for the status of any > database connection > pools configured in the cocoon.xconf (e.g. counts of > open/active/closed > connections and number of requests made), at least when using > the <jdbc> > type pools (j2ee type container-managed datasources are less > important since > the app server would probably have its own monitoring tools > for those). > Seeing as you're already editing the generator, any chance > you could add > that too? ;-) >
Yes, that is quite valuable information as well indeed. I will try to make some time for this one coming week, and will let it know when it is finished (if I succeed). > > > Andrew. > > >From: "Ard Schrijvers" <[EMAIL PROTECTED]> > >Date: Thu, 22 Jun 2006 16:21:40 +0200 > > > >We are using many continuations in our projects, implying > have load on > >memory use (apparantly continuations can be very large in memory..?). > > > >Since in a deployed environment we want to have some idea > about the number > >of continuations out there, I have added this to the > StatusGenerator, in > >the same manner as for the StoreJanitor is done. > > > >Also added to the "Memory" group is the max memory available > >(Runtime.getRuntime().maxMemory()) > > > >Can I send in a patch to have it standard in the StatusGenerator? > > > >Regards ARd > > > >-- > > > >Hippo > >Oosteinde 11 > >1017WT Amsterdam > >The Netherlands > >Tel +31 (0)20 5224466 > >------------------------------------------------------------- > >[EMAIL PROTECTED] / http://www.hippo.nl > >-------------------------------------------------------------- > > >
