I'm envisioning server management functionality. True the current info/features are sparse, but the idea is there. While a lot of information in DefaultKernelMBean is just the configuration stuff, there are a few more tidbits such as memory usage, #threads, etc. I was sort of thinking that after adding functionality to unload/load components on the fly that type of thing would be there as well. Right now I was just wondering if I could get at the thing.
Here is a little more detail about what I thinking - and any thoughts from other on this is appreciated.
* A JMX listener can be plugged into the merlin system as a
privileged component and as such can get access to the root
application container hierarchy. From here it can navigate and
listen to changes (and initiate change navigation). Navigation
allows the listener to inspect a component deployment scenario
which means it has read access to the component type and the
component deployment information. * Using technology from either XDoclet or Phoenix we should be able
to provide supplementary information about a components management
interface (as distinct from service interfaces). A JMX listener
would be able to build up a registry of information (in effect a
registry of MBeans) and register these with an MBean server under
a namespace established by the kernel within which it is executing. * A MerlinMBean needs to be written that contains a full embedded
Merlin instance. This instance would be parameterized exclusively
by properties. It would by default ensure that a model listener
is established that in turn would register manageable component in
the server.I like the direction your going making DefaultKernelMBean service available to components and I think it provides a nice platform on which to add Server mgmt features so that a sysadmin type could feel like they have control/visibility of the server other than just pulling the plug when something isn't working as planned.
Just for clarification/verification concerning the question of availability, here is a summary of who/what would have access to a kernel or component MBeans:
* the merlin kernel * model listeners registered with the kernel * components deployed as dependents of model listeners * the system administrator
This also means that any component deployed in application space will not have access to the management interfaces for reasons of security.
I'm in the early learning stages with 3.2.5 right now, but making progress.
Great - remember - when you find even minor issues with the docs, tutorials, whatever - feedback *will* be appreciated.
BTW, is there a link to the specific enhancements your making to that interface/service?
Not really. As soon as JIRA for Avalon is up we will be able to get a lot more organized on this sort of thing. For now its CVS HEAD + dev mailing list.
Cheers, Stephen.
Thanks for the info Stephen.
Jerry
"Stephen McConnell" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
Jerry Shockley wrote:
I would like to gain access to the DefaultKernelMBean service, but am
unsure
how to configure my block in order to access the service. Has anyone
done
this or have ideas on how to do it?
Under 3.2.X the DefaultKernelMBean is only available to code running inside container space. This means that is accessible to an embedder. Under 3.3 (CVS HEAD) the DefaultKernelMBean class has been removed and will be replaced with an updated implementation that is itself a listener (work in progress stuff).
For reference, what did you have in mind with respect to the DefaultKernelMBean interface. Under 3.3 there are a bunch more options available, some of which may be appropriate.
Stephen.
Thanks, Jerry
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
