Is there a general guide line for domain usage under jmx?  Are there any
plans to exploit this in a more organized manner?  Should domain refer to
components on a single agent, or cross multiple agents?  For example in a
clustered environment, domain could refer to a particular node group, or
could simply refer to a group of components on a single node.

I am thinking that the jmx domain fluff might bet best left as a node
component grouping tools, and leave node grouping up to higher level
organizations (like jini and such).

Any ways, this is going to be important for the upcoming RH stuff to provide
a consistent and rich configuration of JBoss nodes in a farm or clustered
environment.

--jason


On Wed, 15 Aug 2001, David Jencks wrote:

> Hi,
> Are you sure ObjectName(":service=Container,jndiName=someName") really can
> be used to register an mbean? normally the object name is actually set from
> jboss.jcml which always seems to have DefaultDomain/JCA/whatever in the
> name.  Although some mbeans have OBJECT_NAME constants lacking the domain
> (for instance ConnectionFactoryLoader) in my experience these cannot
> actually be used to register instances.
>
> I wonder if DefaultDomain is always appropriate?  Seems to me that we might
> want to put each applications' mbeans in its own domain????
>
> I think also you can get all mbeans in any domain with the desired jndiname
> with
>
> ObjectName("*:service=Container,jndiName=somename").
>
> david jencks
>
> On 2001.08.15 10:43:16 -0400 Scott M Stark wrote:
> > This pattern should be used in both the start and stop methods then. I
> > have done this and I am able to redeploy ejb jars.
> >
> > Why can the name ObjectName(":service=Container,jndiName=someName")
> > be used to register an mbean but the same name fails to unregister it?
> >
> > ----- Original Message -----
> > From: "Vincent Harcq" <[EMAIL PROTECTED]>
> > To: "Dev JBoss" <[EMAIL PROTECTED]>
> > Sent: Wednesday, August 15, 2001 5:19 AM
> > Subject: [JBoss-dev] Container.java
> >
> >
> > > The server can not re-deploy an ejb jar anymore because of exception on
> > > unregistration of MBean.
> > >
> > > Does this makes sense (on the stop() method)?
> > >
> > > diff -r1.55 Container.java
> > > 421c421
> > > <          ObjectName jmxName = new
> > >
> > ObjectName(":service=Container,jndiName="+this.getBeanMetaData().getJndiName
> > > ());
> > > ---
> > > >          ObjectName jmxName = new
> > >
> > ObjectName(mbeanServer.getDefaultDomain()+":service=Container,jndiName="+thi
> > > s.getBeanMetaData().getJndiName());
> > >
> > > Vincent.
> > >
> > >
> > > _________________________________________________________
> > > Do You Yahoo!?
> > > Get your free @yahoo.com address at http://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
> >
> >
>
> _______________________________________________
> 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