Hi,

I've been wondering just how the mbean stuff works so when I saw your
question I looked around a bit.

I am not yet an expert, if I am wrong please correct me.

I think any mbeans registered with the jmx server jboss is using should be
visible on the same web-management page as jboss stuff.  As far as I can
tell jboss is using the sun ri of jmx server, and html adapter.

What exactly happens when you deploy a init-free mbean? Looking at the
ServiceControl mbean, which seems to be what calls init, it appears to
catch and log the fact that the method is missing.  Does it not show up on
the management web page?

The lifecycle methods don't actually have to do anything-- I have not yet
come across a ServiceMBean that implements all 4 methods.  If the exception
is getting you in trouble, adding an empty method should fix it.

I regards to the service groups question, what do you want to do that would
not be satisfied by a jetty domain?

Is your JettyService mbean registering all the other mbeans with the same
mbeanserver that jboss is using?

How are you storing configuration info for your mbeans?

Personally I really like the xml-format .jcml configuration format and
would not mind if everyone else used it too.

So, these are questions rather than answers...I'm pretty interested in how
this will work out.

Thanks
David Jencks




On 2001.04.10 12:40:26 -0400 Julian Gosnell wrote:
> It doesn't go anywhere in JBoss, because it is not
> part of it.
> 
> JBoss kicks off a JettyService (this IS configured in
> jboss.conf and DOES comply with JBoss' lifecycle
> interface).
> 
> JettyService kicks off a JettyMBean which subsequently
> kicks off e.g. HttpListeners, WebApplicationContexts
> etc which are all MBeans. All are part of the inner
> workings of Jetty and have nothing to do with JBoss,
> thus are NOT configured in any JBoss file.
> 
> However, Seeing as Jetty is a Service running within
> JBoss they may be considered subcomponents of JBoss
> and it would therefore be nice to be able to reach
> them from the JMX Agent page, see what they are doing
> and alter settings on them if you so need.
> 
> I'm sure that JMX does not mandate a particular
> lifecycle for MBeans, otherwise the Jetty MBeans would
> share it, so it must be JBoss doing this. 
> 
> So I guess the question is, without rewriting half of
> Jetty, how can I connect Jetty's
> non-JBoss-lifecycle-compliant beans into JBoss' JMX
> architecture ?
> 
> Jules
> 
> --- danch <[EMAIL PROTECTED]> wrote:
> > Have you tried putting the jetty <mbean> stuff in
> > jboss.conf rather than
> > jboss.jcml? I believe (but I'm not a JMX expert)
> > that the Service
> > (init,start,stop,destroy) only applies to mbeans
> > listed in jboss.jcml,
> > not those in jboss.conf.
> > 
> > Julian Gosnell wrote:
> > > 
> > > Greg has released JettyJMX, a packaged which
> > > integrates with Jetty in order that all major
> > > components of Jetty become MBeans.
> > > 
> > > I have been integrating this into jboss_jetty, so
> > that
> > > Jetty is now listed by the JMX agent as a
> > collection
> > > of services, all with published interfaces,
> > instead of
> > > one megalithic service.
> > > 
> > > I have a problem !
> > > 
> > > JBoss seems to expect MBeans registered with it's
> > JMX
> > > Server to support a JBoss-inspired life-cycle
> > > init()/start()/stop()/destroy().
> > > 
> > > Jetty MBeans support a different lifecycle which
> > has
> > > no init() method.
> > > 
> > > Every time a Jetty MBean is registered, JBoss
> > tries to
> > > call it's init() method, resulting in an exception
> > > being thrown from within JMX.
> > > 
> > > Maybe I am taking the wrong approach.
> > > 
> > > I would like internal Jetty services to be
> > available
> > > to JBoss users via JMX. However these internal
> > > services should be managed by Jetty, not JBoss (I
> > > don't expect someone else to come in and call
> > > lifecycle methods on objects I own...)
> > > 
> > > Can this be done ?
> > > 
> > > Do I register Jetty MBeans against another JMX
> > Server
> > > ? If so can I hook this into the main JBoss one ?
> > > 
> > > Should JBoss-Jetty actually be this JMX Server ?
> > > 
> > > How should we scope groups of nested services
> > within
> > > JBoss ?
> > > 
> > > That should do it !
> > > 
> > > Jules
> > > 
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Get email at your own domain with Yahoo! Mail.
> > > http://personal.mail.yahoo.com/
> > > 
> > > _______________________________________________
> > > Jboss-development mailing list
> > > [EMAIL PROTECTED]
> > >
> >
> http://lists.sourceforge.net/lists/listinfo/jboss-development
> > Confidential e-mail for addressee only.  Access to
> > this e-mail by anyone else is unauthorized.
> > If you have received this message in error, please
> > notify the sender immediately by reply e-mail 
> > and destroy the original communication.
> > 
> > 
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> >
> http://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail. 
> http://personal.mail.yahoo.com/
> 
> _______________________________________________
> 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

Reply via email to