Just one word:
IMPRESSIVE !
Simon
> -----Original Message-----
> From: Stacy Curl [mailto:[EMAIL PROTECTED]]
> Sent: venerdì 6 aprile 2001 11:59
> To: '[EMAIL PROTECTED]'; 'Andreas Schaefer'
> Subject: [JBoss-dev] JMX in jBoss, Clustering, Monitoring, Failover,
> better bootstrapp ing via pluggable XMLet
>
>
> Hello, I'd like to tell you about the code that I've developed and
> contributed to JBoss.
>
> I've developed some code to augment the basic capabilities
> that JMX gives
> you. I've written an MBean that will 'mirror' MBeans, that is
> it will take a
> subset of MBeans on one JMX agent and create proxies for them
> on another JMX
> agent (the idea of proxying is wide place but the inspiration for this
> instance was taken from the CascadingAgent from JDMK).
>
> Secondly I've created a 'Watchdog' MBean that monitors the health of
> 'Watchable' (*) MBeans and calls restart on the watchable
> MBeans when they
> have failed. I've also wrapped the JMX agent in an RMI
> Activatable object so
> that the whole JMX agent itself can be restarted (also by the
> Watchdog) in
> the event that JVM dies.
> (*) Actually they are called 'startable' and should be renamed to
> 'watchable'.
>
> I've also rewritten the MLet loading class as a pluggable
> XMLet loading
> class, using this method I've been able to specify in the
> XMLet resource
> file which MBeans are critical (failure to start means the
> JMX agent is
> useless) to optional (failure to start leaves the JMX agent still
> functional).
>
> The stuff I wrote can be found at
> http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/jbossmx/?cvsroot=jboss
>
> I wrote all of this not out of the goodness of my own heart
> but because my
> company needed the capability to monitor and restart its Java
> code, the Java
> code needed absolutely to create threads and so couldn't be
> written as EJB,
> so I had to devise a skeleton failover / high availability
> system outside of
> an app server. Fortunately my company doesn't ever plan to go into the
> failover / monitoring business so they were comfortable with
> me placing the
> code in JBoss. This also means that I'll be adding more
> features to JBoss in
> the future and getting paid for it :). Of course this point
> is moot if those
> features are not interesting to the JBoss group.
>
> Since JBoss is based on JMX and will in the near future have
> a number of JMX
> Agents to enable clustering of the EJB Containers then
> monitoring of these
> Agents and containers seem crucial, there is much work to be
> done but I
> think that my code should serve as a reasonable base.
>
> Ideas for the future:
> - Have multiple JMX Agent (got), but specify a single XMLet
> resource file,
> let the MBeans be distributed evenly across the Agents, this
> is called a
> Single System Image (SSI JMX)
> - Offer different styles of monitoring, currently it's poll
> based, could use
> a 'dead-man's handle', or pure event based monitoring,
> combinations also
> possible.
> - Are there parallels between JMX and RMI, there is an
> RMIRegistry, does it
> make sense to have a JMXRegistry and access the MBeans through URL's ?
> jmx://machineName:agentName/domainName/objectName or
> jmx://agentName/domainName/objectName, or in conjunction with
> the SSI JMX:
> jmx://domainName/objectName
> - Current system offers emails when corrective action is
> taken on a failed
> MBean, future system could monitor performance and email on crossing
> critical boundaries (90% maximum I/O, memory, etc).
> - Can only send emails to support staff at present, other
> possibilities may
> be useful such as sending pagers.
> - Can only see (in the HTML view) the current state of the
> system, it would
> be useful to be able to run through a movie of previous
> states and also
> highlight differences.
> - The HTML view is quite minimal, I've created a pluggable
> version which
> enables MBeans to specify somewhat their display, this can be improved
> significantly which will aide support staff.
>
> --- Brain Dump ENDS ------
>
> Regards,
> Stacy.
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
