Yes I have and yes I will :-) I *may* submit this in the patch when I've sorted the mess out. -- Jason
> -----Original Message----- > From: Steve Short [mailto:[EMAIL PROTECTED]] > Sent: 23 August 2002 18:16 > To: James Developers List > Subject: RE: [PATCH]Simple stats and monitoring for James > > > Jason, > > Did you consider using JMX to expose various objects for > managements? I haven't been able to play with the latest > Avalon and James stuff myself, but I was hoping to use the > JMX stuff to list repositories, repository queue lengths etc. > This would enable James to be monitored using any JMX > capable monitoring tool. > > Regards > Steve > > > > -----Original Message----- > > From: Harmeet Bedi [mailto:[EMAIL PROTECTED]] > > Sent: Friday, August 23, 2002 8:44 AM > > To: James Developers List > > Subject: Re: [PATCH]Simple stats and monitoring for James > > > > > > Would it be better/possible to leverage logger interface for > > stats ? Would it be possible for the API to take a stats > > object rather than separate parameters. One advantage is that > > string construction is done only if stats logging is enabled. > > > > Would it be possible to use int instead of float. The > > advantage is that int based counters can be shared across > > threads without the need to synchronize. > > > > Instead of > > import ...*; > > It is prefered to have the fully qualified class name. > > It is painful, but here is a way to reduce the pain: > > jad -p -pi1000 <classname> | grep "^import" > > > > where jad is java decompiler. Excellent tool. > > > > > If I've missed anything out, or screwed something up, > just email me > > > directly, rather than clog up the list with stuff that > most people > > > couldn't care about. > > > > Looks like a very necessary thing for a system to have. I am > > sending email to the list because I thought some of the > > issues like jad, api etc. may interest others. > > > > Harmeet > > > > ----- Original Message ----- > > From: "Jason Webb" <[EMAIL PROTECTED]> > > Subject: [PATCH]Simple stats and monitoring for James > > > > > > > Please find enclosed my attempt at a simple stats and monitoring > > > package for James. There are two main ways for getting the stats > > > information out at the > > > moment: > > > Via. the remote manager, > > > Or via a stats log file (mainly used for MRTG style monitoring) > > > > > > If I've missed anything out, or screwed something up, > just email me > > > directly, rather than clog up the list with stuff that > most people > > > couldn't care about. > > > > > > I've attached a zip file with the patch files as well as > > the new ones. > > > Patch files are zip'd flat, the new files in the their correct > > > directories. > > > > > > -- Jason > > > > > > > > > -------------------------------------------------------------- > > -------------- > > ---- > > > > > > > -- > > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:james-dev-> [EMAIL PROTECTED]> > > For > > additional commands, > > e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > -- > To unsubscribe, e-mail: > <mailto:james-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
