You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Adam Wojtuniak (JIRA)" <ji...@apache.org> on 2009/10/21 23:08:59 UTC
[jira] Created: (ARIES-29) Implement JMX Agent
Implement JMX Agent
-------------------
Key: ARIES-29
URL: https://issues.apache.org/jira/browse/ARIES-29
Project: Aries
Issue Type: New Feature
Components: JMX
Affects Versions: 1.0
Reporter: Adam Wojtuniak
Fix For: 1.0
Implement JMX Agent. It should be responsible for tracking all MBean servers(registered as a services) and services which will be exposed as a Managed Beans (MBeans).
JMX Agent should register following MBeans: Framework MBean, Bundle State MBean, Service State MBean, Package State MBean, Permission Admin MBean, Configuration Admin MBean,
Provisioning Service MBean, User Admin MBean, Conditional Permission Admin MBean.
It is open issue if we should track MBean servers registered as services but for now we can follow RI of JMX which listen to MBean Server services.
For now we can track MBeanServers and when service is discovered register MBeans. Same in case when service is exposed as Managed MBeans it should be registered (on all available MBean servers) when is discovered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (ARIES-29) Implement JMX Agent
Posted by adam wojtuniak <ad...@gmail.com>.
Hi Alasdair
Yes this is correct.
I don't want to have everything in the Activator like it is in RI.
JMXAgentContext is injected to the trackers with this design they don't need
to be directly depend on jmxagent.
Example code from MBeanServiceTracker:
public Object addingService(final ServiceReference reference) {
executor.submit(new Runnable() {
public void run() {
BundleContext bc = agentContext.getBundleContext();
MBeanServer mbeanServer = (MBeanServer)
bc.getService(reference);
agentContext.registerServices(mbeanServer);
}
});
return super.addingService(reference);
}
Cheers,
Adam
On Mon, Oct 26, 2009 at 5:45 PM, Alasdair Nottingham <
alasdair.nottingham@gmail.com> wrote:
> I want to check I've understood what you are proposing so I'm going to
> reword and repeat back.
>
> The JMXAgent will track registered MBean servers. It will also track
> services that can be exposed using the specified MBeans. When a
> service, such as the UserAdmin service, is registered the tracker will
> spot this and register the UserAdmin MBean with any MBean servers
> registered in the service registry.
>
> It is not clear to me what API the JMXAgent needs to provide, and I'm
> not sure I understand what the JMXAgentContext is for.
>
> The agent will not be looking for MBeans registered in the service
> registry.
>
> Is this correct?
> Alasdair
>
> 2009/10/25 adam wojtuniak <ad...@gmail.com>:
> > Hi Alasdair
> >
> > My propsal is that JMXAgent will track registered MBean servers and
> there
> > also will be trackers for
> > services which are exposed as a MBeans. JMXAgent will provide methods for
> > registration of MBeans and JMXAgentContext will be provided (mainly
> delegate
> > registration methods to agent).
> > Context will be used by trackers to register MBean or MBeans
> > (MBeanServiceTracker).
> > Trackers of services exposed as a MBeans also will register or unregister
> > MBean.
> > There will be no MBeans registered in ServiceRegistry.
> > I've already done some implemenation of Agent, trackers etc.
> >
> > Cheers,
> > Adam
> >
> > On Sun, Oct 25, 2009 at 6:56 PM, Alasdair Nottingham <
> > alasdair.nottingham@gmail.com> wrote:
> >
> >> The problem I have here is that it is not clear to me how this really
> >> helps with the goal of making the components "easily consumed". My
> >> understanding of the JIRA is that it will track MBeans registered in
> >> the service registry and when it sees one it will register it with any
> >> MBeanServers registered in the service registry. So to "consume" the
> >> JMX Mbeans using the agent I need to create an MBeanServer and
> >> register it in the service registry, and then create the MBeans and
> >> also register them in the service registry. As a consumer I could just
> >> as easily construct the MBeans myself and register them without going
> >> via the service registry.
> >>
> >> I'm just not sure what the goal of creating this JMX Agent is. Reading
> >> the JIRA I wonder if it has been raised mainly because the RI does
> >> something similar.
> >>
> >> Alasdair
> >>
> >> 2009/10/22 Guillaume Nodet <gn...@gmail.com>:
> >> > I think when such a problem arise, we need to do the following:
> >> > * provide a default and simple implementation
> >> > * make sure the implementation is easily pluggable so that aries
> >> > consumers can easily replace the part with something more stuitable
> >> > for their runtime
> >> > I think the first point is important in order for basic users to be
> >> > able to use aries components easily, have them deployed in an osgi
> >> > runtime without requiring additional coding. This will help
> >> > attracting more people and grow the users community (and hopefully
> >> > then, the developers community). If we don't provide components that
> >> > can be used directly, people will just go away.
> >> > The second point is necessary to fullfil the requirements you
> >> > expressed: i.e. when you embed an aries component into a given
> >> > runtime, you may need a tighter integration with the runtime, hence
> >> > the need for pluggable parts to replace.
> >> >
> >> > In our case, a simple solution would be to have a simple module that
> >> > will grab or create a default platform mbean server and register it in
> >> > osgi. We could leave out creating a remote jmx connector and all, as
> >> > this would soon have ties to the security bits and such ...
> >> >
> >> > On Thu, Oct 22, 2009 at 21:58, Alasdair Nottingham
> >> > <al...@gmail.com> wrote:
> >> >> Hi,
> >> >>
> >> >> The JMX specification (taken from the March early draft) says the
> >> >> following about the MBean server:
> >> >>
> >> >> "The construction, maintenance and lifecycle of the MBeanServer which
> >> >> will host the MBeans defined in this specification is intentionally
> >> >> left undefined. It is left undefined as the MBeanServer is invariably
> >> >> tied to the particular application that is responsible for it. For
> >> >> example, the MBeanServer may exist outside the OSGi framework that
> the
> >> >> MBeans are managing. Or there may be multiple MBean servers which
> >> >> contain the MBeans defined in this specification. The introduction of
> >> >> nested frameworks, such as those defined in RFC 138, may have their
> >> >> management MBeans hosted in the MBeanServer which hosts the MBeans
> for
> >> >> the outermost OSGi container. Alternatively, these MBeans may be
> >> >> hosted, for example, in an application server's MBeanServer which is
> >> >> embedding mulitple OSGi containers."
> >> >>
> >> >> My interpretation of this is that the specification does not describe
> >> >> how the MBeans are registered with an MBean server. So this JIRA
> seems
> >> >> to go beyond what is required to implement the JMX specification.
> >> >>
> >> >> This is not necessarily a problem, but it does make me wonder if
> doing
> >> >> this work is in the scope of the original incubator proposal. I think
> >> >> registration of MBeans with an MBeanServer is the responsibility of
> >> >> the runtime into which Aries has been embedded rather than the aries
> >> >> podling itself.
> >> >>
> >> >> What do people think?
> >> >> Alasdair
> >> >>
> >> >> 2009/10/21 Adam Wojtuniak (JIRA) <ji...@apache.org>:
> >> >>> Implement JMX Agent
> >> >>> -------------------
> >> >>>
> >> >>> Key: ARIES-29
> >> >>> URL: https://issues.apache.org/jira/browse/ARIES-29
> >> >>> Project: Aries
> >> >>> Issue Type: New Feature
> >> >>> Components: JMX
> >> >>> Affects Versions: 1.0
> >> >>> Reporter: Adam Wojtuniak
> >> >>> Fix For: 1.0
> >> >>>
> >> >>>
> >> >>> Implement JMX Agent. It should be responsible for tracking all MBean
> >> servers(registered as a services) and services which will be exposed as
> a
> >> Managed Beans (MBeans).
> >> >>> JMX Agent should register following MBeans: Framework MBean, Bundle
> >> State MBean, Service State MBean, Package State MBean, Permission Admin
> >> MBean, Configuration Admin MBean,
> >> >>> Provisioning Service MBean, User Admin MBean, Conditional Permission
> >> Admin MBean.
> >> >>> It is open issue if we should track MBean servers registered as
> >> services but for now we can follow RI of JMX which listen to MBean
> Server
> >> services.
> >> >>> For now we can track MBeanServers and when service is discovered
> >> register MBeans. Same in case when service is exposed as Managed MBeans
> it
> >> should be registered (on all available MBean servers) when is
> discovered.
> >> >>>
> >> >>> --
> >> >>> This message is automatically generated by JIRA.
> >> >>> -
> >> >>> You can reply to this email to add a comment to the issue online.
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Alasdair Nottingham
> >> >> alasdair.nottingham@gmail.com
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Cheers,
> >> > Guillaume Nodet
> >> > ------------------------
> >> > Blog: http://gnodet.blogspot.com/
> >> > ------------------------
> >> > Open Source SOA
> >> > http://fusesource.com
> >> >
> >>
> >>
> >>
> >> --
> >> Alasdair Nottingham
> >> alasdair.nottingham@gmail.com
> >>
> >
>
>
>
> --
> Alasdair Nottingham
> alasdair.nottingham@gmail.com
>
Re: [jira] Created: (ARIES-29) Implement JMX Agent
Posted by Alasdair Nottingham <al...@gmail.com>.
I want to check I've understood what you are proposing so I'm going to
reword and repeat back.
The JMXAgent will track registered MBean servers. It will also track
services that can be exposed using the specified MBeans. When a
service, such as the UserAdmin service, is registered the tracker will
spot this and register the UserAdmin MBean with any MBean servers
registered in the service registry.
It is not clear to me what API the JMXAgent needs to provide, and I'm
not sure I understand what the JMXAgentContext is for.
The agent will not be looking for MBeans registered in the service registry.
Is this correct?
Alasdair
2009/10/25 adam wojtuniak <ad...@gmail.com>:
> Hi Alasdair
>
> My propsal is that JMXAgent will track registered MBean servers and there
> also will be trackers for
> services which are exposed as a MBeans. JMXAgent will provide methods for
> registration of MBeans and JMXAgentContext will be provided (mainly delegate
> registration methods to agent).
> Context will be used by trackers to register MBean or MBeans
> (MBeanServiceTracker).
> Trackers of services exposed as a MBeans also will register or unregister
> MBean.
> There will be no MBeans registered in ServiceRegistry.
> I've already done some implemenation of Agent, trackers etc.
>
> Cheers,
> Adam
>
> On Sun, Oct 25, 2009 at 6:56 PM, Alasdair Nottingham <
> alasdair.nottingham@gmail.com> wrote:
>
>> The problem I have here is that it is not clear to me how this really
>> helps with the goal of making the components "easily consumed". My
>> understanding of the JIRA is that it will track MBeans registered in
>> the service registry and when it sees one it will register it with any
>> MBeanServers registered in the service registry. So to "consume" the
>> JMX Mbeans using the agent I need to create an MBeanServer and
>> register it in the service registry, and then create the MBeans and
>> also register them in the service registry. As a consumer I could just
>> as easily construct the MBeans myself and register them without going
>> via the service registry.
>>
>> I'm just not sure what the goal of creating this JMX Agent is. Reading
>> the JIRA I wonder if it has been raised mainly because the RI does
>> something similar.
>>
>> Alasdair
>>
>> 2009/10/22 Guillaume Nodet <gn...@gmail.com>:
>> > I think when such a problem arise, we need to do the following:
>> > * provide a default and simple implementation
>> > * make sure the implementation is easily pluggable so that aries
>> > consumers can easily replace the part with something more stuitable
>> > for their runtime
>> > I think the first point is important in order for basic users to be
>> > able to use aries components easily, have them deployed in an osgi
>> > runtime without requiring additional coding. This will help
>> > attracting more people and grow the users community (and hopefully
>> > then, the developers community). If we don't provide components that
>> > can be used directly, people will just go away.
>> > The second point is necessary to fullfil the requirements you
>> > expressed: i.e. when you embed an aries component into a given
>> > runtime, you may need a tighter integration with the runtime, hence
>> > the need for pluggable parts to replace.
>> >
>> > In our case, a simple solution would be to have a simple module that
>> > will grab or create a default platform mbean server and register it in
>> > osgi. We could leave out creating a remote jmx connector and all, as
>> > this would soon have ties to the security bits and such ...
>> >
>> > On Thu, Oct 22, 2009 at 21:58, Alasdair Nottingham
>> > <al...@gmail.com> wrote:
>> >> Hi,
>> >>
>> >> The JMX specification (taken from the March early draft) says the
>> >> following about the MBean server:
>> >>
>> >> "The construction, maintenance and lifecycle of the MBeanServer which
>> >> will host the MBeans defined in this specification is intentionally
>> >> left undefined. It is left undefined as the MBeanServer is invariably
>> >> tied to the particular application that is responsible for it. For
>> >> example, the MBeanServer may exist outside the OSGi framework that the
>> >> MBeans are managing. Or there may be multiple MBean servers which
>> >> contain the MBeans defined in this specification. The introduction of
>> >> nested frameworks, such as those defined in RFC 138, may have their
>> >> management MBeans hosted in the MBeanServer which hosts the MBeans for
>> >> the outermost OSGi container. Alternatively, these MBeans may be
>> >> hosted, for example, in an application server's MBeanServer which is
>> >> embedding mulitple OSGi containers."
>> >>
>> >> My interpretation of this is that the specification does not describe
>> >> how the MBeans are registered with an MBean server. So this JIRA seems
>> >> to go beyond what is required to implement the JMX specification.
>> >>
>> >> This is not necessarily a problem, but it does make me wonder if doing
>> >> this work is in the scope of the original incubator proposal. I think
>> >> registration of MBeans with an MBeanServer is the responsibility of
>> >> the runtime into which Aries has been embedded rather than the aries
>> >> podling itself.
>> >>
>> >> What do people think?
>> >> Alasdair
>> >>
>> >> 2009/10/21 Adam Wojtuniak (JIRA) <ji...@apache.org>:
>> >>> Implement JMX Agent
>> >>> -------------------
>> >>>
>> >>> Key: ARIES-29
>> >>> URL: https://issues.apache.org/jira/browse/ARIES-29
>> >>> Project: Aries
>> >>> Issue Type: New Feature
>> >>> Components: JMX
>> >>> Affects Versions: 1.0
>> >>> Reporter: Adam Wojtuniak
>> >>> Fix For: 1.0
>> >>>
>> >>>
>> >>> Implement JMX Agent. It should be responsible for tracking all MBean
>> servers(registered as a services) and services which will be exposed as a
>> Managed Beans (MBeans).
>> >>> JMX Agent should register following MBeans: Framework MBean, Bundle
>> State MBean, Service State MBean, Package State MBean, Permission Admin
>> MBean, Configuration Admin MBean,
>> >>> Provisioning Service MBean, User Admin MBean, Conditional Permission
>> Admin MBean.
>> >>> It is open issue if we should track MBean servers registered as
>> services but for now we can follow RI of JMX which listen to MBean Server
>> services.
>> >>> For now we can track MBeanServers and when service is discovered
>> register MBeans. Same in case when service is exposed as Managed MBeans it
>> should be registered (on all available MBean servers) when is discovered.
>> >>>
>> >>> --
>> >>> This message is automatically generated by JIRA.
>> >>> -
>> >>> You can reply to this email to add a comment to the issue online.
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Alasdair Nottingham
>> >> alasdair.nottingham@gmail.com
>> >>
>> >
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> > ------------------------
>> > Blog: http://gnodet.blogspot.com/
>> > ------------------------
>> > Open Source SOA
>> > http://fusesource.com
>> >
>>
>>
>>
>> --
>> Alasdair Nottingham
>> alasdair.nottingham@gmail.com
>>
>
--
Alasdair Nottingham
alasdair.nottingham@gmail.com
Re: [jira] Created: (ARIES-29) Implement JMX Agent
Posted by adam wojtuniak <ad...@gmail.com>.
Hi Alasdair
My propsal is that JMXAgent will track registered MBean servers and there
also will be trackers for
services which are exposed as a MBeans. JMXAgent will provide methods for
registration of MBeans and JMXAgentContext will be provided (mainly delegate
registration methods to agent).
Context will be used by trackers to register MBean or MBeans
(MBeanServiceTracker).
Trackers of services exposed as a MBeans also will register or unregister
MBean.
There will be no MBeans registered in ServiceRegistry.
I've already done some implemenation of Agent, trackers etc.
Cheers,
Adam
On Sun, Oct 25, 2009 at 6:56 PM, Alasdair Nottingham <
alasdair.nottingham@gmail.com> wrote:
> The problem I have here is that it is not clear to me how this really
> helps with the goal of making the components "easily consumed". My
> understanding of the JIRA is that it will track MBeans registered in
> the service registry and when it sees one it will register it with any
> MBeanServers registered in the service registry. So to "consume" the
> JMX Mbeans using the agent I need to create an MBeanServer and
> register it in the service registry, and then create the MBeans and
> also register them in the service registry. As a consumer I could just
> as easily construct the MBeans myself and register them without going
> via the service registry.
>
> I'm just not sure what the goal of creating this JMX Agent is. Reading
> the JIRA I wonder if it has been raised mainly because the RI does
> something similar.
>
> Alasdair
>
> 2009/10/22 Guillaume Nodet <gn...@gmail.com>:
> > I think when such a problem arise, we need to do the following:
> > * provide a default and simple implementation
> > * make sure the implementation is easily pluggable so that aries
> > consumers can easily replace the part with something more stuitable
> > for their runtime
> > I think the first point is important in order for basic users to be
> > able to use aries components easily, have them deployed in an osgi
> > runtime without requiring additional coding. This will help
> > attracting more people and grow the users community (and hopefully
> > then, the developers community). If we don't provide components that
> > can be used directly, people will just go away.
> > The second point is necessary to fullfil the requirements you
> > expressed: i.e. when you embed an aries component into a given
> > runtime, you may need a tighter integration with the runtime, hence
> > the need for pluggable parts to replace.
> >
> > In our case, a simple solution would be to have a simple module that
> > will grab or create a default platform mbean server and register it in
> > osgi. We could leave out creating a remote jmx connector and all, as
> > this would soon have ties to the security bits and such ...
> >
> > On Thu, Oct 22, 2009 at 21:58, Alasdair Nottingham
> > <al...@gmail.com> wrote:
> >> Hi,
> >>
> >> The JMX specification (taken from the March early draft) says the
> >> following about the MBean server:
> >>
> >> "The construction, maintenance and lifecycle of the MBeanServer which
> >> will host the MBeans defined in this specification is intentionally
> >> left undefined. It is left undefined as the MBeanServer is invariably
> >> tied to the particular application that is responsible for it. For
> >> example, the MBeanServer may exist outside the OSGi framework that the
> >> MBeans are managing. Or there may be multiple MBean servers which
> >> contain the MBeans defined in this specification. The introduction of
> >> nested frameworks, such as those defined in RFC 138, may have their
> >> management MBeans hosted in the MBeanServer which hosts the MBeans for
> >> the outermost OSGi container. Alternatively, these MBeans may be
> >> hosted, for example, in an application server's MBeanServer which is
> >> embedding mulitple OSGi containers."
> >>
> >> My interpretation of this is that the specification does not describe
> >> how the MBeans are registered with an MBean server. So this JIRA seems
> >> to go beyond what is required to implement the JMX specification.
> >>
> >> This is not necessarily a problem, but it does make me wonder if doing
> >> this work is in the scope of the original incubator proposal. I think
> >> registration of MBeans with an MBeanServer is the responsibility of
> >> the runtime into which Aries has been embedded rather than the aries
> >> podling itself.
> >>
> >> What do people think?
> >> Alasdair
> >>
> >> 2009/10/21 Adam Wojtuniak (JIRA) <ji...@apache.org>:
> >>> Implement JMX Agent
> >>> -------------------
> >>>
> >>> Key: ARIES-29
> >>> URL: https://issues.apache.org/jira/browse/ARIES-29
> >>> Project: Aries
> >>> Issue Type: New Feature
> >>> Components: JMX
> >>> Affects Versions: 1.0
> >>> Reporter: Adam Wojtuniak
> >>> Fix For: 1.0
> >>>
> >>>
> >>> Implement JMX Agent. It should be responsible for tracking all MBean
> servers(registered as a services) and services which will be exposed as a
> Managed Beans (MBeans).
> >>> JMX Agent should register following MBeans: Framework MBean, Bundle
> State MBean, Service State MBean, Package State MBean, Permission Admin
> MBean, Configuration Admin MBean,
> >>> Provisioning Service MBean, User Admin MBean, Conditional Permission
> Admin MBean.
> >>> It is open issue if we should track MBean servers registered as
> services but for now we can follow RI of JMX which listen to MBean Server
> services.
> >>> For now we can track MBeanServers and when service is discovered
> register MBeans. Same in case when service is exposed as Managed MBeans it
> should be registered (on all available MBean servers) when is discovered.
> >>>
> >>> --
> >>> This message is automatically generated by JIRA.
> >>> -
> >>> You can reply to this email to add a comment to the issue online.
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> Alasdair Nottingham
> >> alasdair.nottingham@gmail.com
> >>
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> > ------------------------
> > Open Source SOA
> > http://fusesource.com
> >
>
>
>
> --
> Alasdair Nottingham
> alasdair.nottingham@gmail.com
>
Re: [jira] Created: (ARIES-29) Implement JMX Agent
Posted by Alasdair Nottingham <al...@gmail.com>.
The problem I have here is that it is not clear to me how this really
helps with the goal of making the components "easily consumed". My
understanding of the JIRA is that it will track MBeans registered in
the service registry and when it sees one it will register it with any
MBeanServers registered in the service registry. So to "consume" the
JMX Mbeans using the agent I need to create an MBeanServer and
register it in the service registry, and then create the MBeans and
also register them in the service registry. As a consumer I could just
as easily construct the MBeans myself and register them without going
via the service registry.
I'm just not sure what the goal of creating this JMX Agent is. Reading
the JIRA I wonder if it has been raised mainly because the RI does
something similar.
Alasdair
2009/10/22 Guillaume Nodet <gn...@gmail.com>:
> I think when such a problem arise, we need to do the following:
> * provide a default and simple implementation
> * make sure the implementation is easily pluggable so that aries
> consumers can easily replace the part with something more stuitable
> for their runtime
> I think the first point is important in order for basic users to be
> able to use aries components easily, have them deployed in an osgi
> runtime without requiring additional coding. This will help
> attracting more people and grow the users community (and hopefully
> then, the developers community). If we don't provide components that
> can be used directly, people will just go away.
> The second point is necessary to fullfil the requirements you
> expressed: i.e. when you embed an aries component into a given
> runtime, you may need a tighter integration with the runtime, hence
> the need for pluggable parts to replace.
>
> In our case, a simple solution would be to have a simple module that
> will grab or create a default platform mbean server and register it in
> osgi. We could leave out creating a remote jmx connector and all, as
> this would soon have ties to the security bits and such ...
>
> On Thu, Oct 22, 2009 at 21:58, Alasdair Nottingham
> <al...@gmail.com> wrote:
>> Hi,
>>
>> The JMX specification (taken from the March early draft) says the
>> following about the MBean server:
>>
>> "The construction, maintenance and lifecycle of the MBeanServer which
>> will host the MBeans defined in this specification is intentionally
>> left undefined. It is left undefined as the MBeanServer is invariably
>> tied to the particular application that is responsible for it. For
>> example, the MBeanServer may exist outside the OSGi framework that the
>> MBeans are managing. Or there may be multiple MBean servers which
>> contain the MBeans defined in this specification. The introduction of
>> nested frameworks, such as those defined in RFC 138, may have their
>> management MBeans hosted in the MBeanServer which hosts the MBeans for
>> the outermost OSGi container. Alternatively, these MBeans may be
>> hosted, for example, in an application server's MBeanServer which is
>> embedding mulitple OSGi containers."
>>
>> My interpretation of this is that the specification does not describe
>> how the MBeans are registered with an MBean server. So this JIRA seems
>> to go beyond what is required to implement the JMX specification.
>>
>> This is not necessarily a problem, but it does make me wonder if doing
>> this work is in the scope of the original incubator proposal. I think
>> registration of MBeans with an MBeanServer is the responsibility of
>> the runtime into which Aries has been embedded rather than the aries
>> podling itself.
>>
>> What do people think?
>> Alasdair
>>
>> 2009/10/21 Adam Wojtuniak (JIRA) <ji...@apache.org>:
>>> Implement JMX Agent
>>> -------------------
>>>
>>> Key: ARIES-29
>>> URL: https://issues.apache.org/jira/browse/ARIES-29
>>> Project: Aries
>>> Issue Type: New Feature
>>> Components: JMX
>>> Affects Versions: 1.0
>>> Reporter: Adam Wojtuniak
>>> Fix For: 1.0
>>>
>>>
>>> Implement JMX Agent. It should be responsible for tracking all MBean servers(registered as a services) and services which will be exposed as a Managed Beans (MBeans).
>>> JMX Agent should register following MBeans: Framework MBean, Bundle State MBean, Service State MBean, Package State MBean, Permission Admin MBean, Configuration Admin MBean,
>>> Provisioning Service MBean, User Admin MBean, Conditional Permission Admin MBean.
>>> It is open issue if we should track MBean servers registered as services but for now we can follow RI of JMX which listen to MBean Server services.
>>> For now we can track MBeanServers and when service is discovered register MBeans. Same in case when service is exposed as Managed MBeans it should be registered (on all available MBean servers) when is discovered.
>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> -
>>> You can reply to this email to add a comment to the issue online.
>>>
>>>
>>
>>
>>
>> --
>> Alasdair Nottingham
>> alasdair.nottingham@gmail.com
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
--
Alasdair Nottingham
alasdair.nottingham@gmail.com
Re: [jira] Created: (ARIES-29) Implement JMX Agent
Posted by Guillaume Nodet <gn...@gmail.com>.
I think when such a problem arise, we need to do the following:
* provide a default and simple implementation
* make sure the implementation is easily pluggable so that aries
consumers can easily replace the part with something more stuitable
for their runtime
I think the first point is important in order for basic users to be
able to use aries components easily, have them deployed in an osgi
runtime without requiring additional coding. This will help
attracting more people and grow the users community (and hopefully
then, the developers community). If we don't provide components that
can be used directly, people will just go away.
The second point is necessary to fullfil the requirements you
expressed: i.e. when you embed an aries component into a given
runtime, you may need a tighter integration with the runtime, hence
the need for pluggable parts to replace.
In our case, a simple solution would be to have a simple module that
will grab or create a default platform mbean server and register it in
osgi. We could leave out creating a remote jmx connector and all, as
this would soon have ties to the security bits and such ...
On Thu, Oct 22, 2009 at 21:58, Alasdair Nottingham
<al...@gmail.com> wrote:
> Hi,
>
> The JMX specification (taken from the March early draft) says the
> following about the MBean server:
>
> "The construction, maintenance and lifecycle of the MBeanServer which
> will host the MBeans defined in this specification is intentionally
> left undefined. It is left undefined as the MBeanServer is invariably
> tied to the particular application that is responsible for it. For
> example, the MBeanServer may exist outside the OSGi framework that the
> MBeans are managing. Or there may be multiple MBean servers which
> contain the MBeans defined in this specification. The introduction of
> nested frameworks, such as those defined in RFC 138, may have their
> management MBeans hosted in the MBeanServer which hosts the MBeans for
> the outermost OSGi container. Alternatively, these MBeans may be
> hosted, for example, in an application server's MBeanServer which is
> embedding mulitple OSGi containers."
>
> My interpretation of this is that the specification does not describe
> how the MBeans are registered with an MBean server. So this JIRA seems
> to go beyond what is required to implement the JMX specification.
>
> This is not necessarily a problem, but it does make me wonder if doing
> this work is in the scope of the original incubator proposal. I think
> registration of MBeans with an MBeanServer is the responsibility of
> the runtime into which Aries has been embedded rather than the aries
> podling itself.
>
> What do people think?
> Alasdair
>
> 2009/10/21 Adam Wojtuniak (JIRA) <ji...@apache.org>:
>> Implement JMX Agent
>> -------------------
>>
>> Key: ARIES-29
>> URL: https://issues.apache.org/jira/browse/ARIES-29
>> Project: Aries
>> Issue Type: New Feature
>> Components: JMX
>> Affects Versions: 1.0
>> Reporter: Adam Wojtuniak
>> Fix For: 1.0
>>
>>
>> Implement JMX Agent. It should be responsible for tracking all MBean servers(registered as a services) and services which will be exposed as a Managed Beans (MBeans).
>> JMX Agent should register following MBeans: Framework MBean, Bundle State MBean, Service State MBean, Package State MBean, Permission Admin MBean, Configuration Admin MBean,
>> Provisioning Service MBean, User Admin MBean, Conditional Permission Admin MBean.
>> It is open issue if we should track MBean servers registered as services but for now we can follow RI of JMX which listen to MBean Server services.
>> For now we can track MBeanServers and when service is discovered register MBeans. Same in case when service is exposed as Managed MBeans it should be registered (on all available MBean servers) when is discovered.
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>
>
>
> --
> Alasdair Nottingham
> alasdair.nottingham@gmail.com
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: [jira] Created: (ARIES-29) Implement JMX Agent
Posted by Alasdair Nottingham <al...@gmail.com>.
Hi,
The JMX specification (taken from the March early draft) says the
following about the MBean server:
"The construction, maintenance and lifecycle of the MBeanServer which
will host the MBeans defined in this specification is intentionally
left undefined. It is left undefined as the MBeanServer is invariably
tied to the particular application that is responsible for it. For
example, the MBeanServer may exist outside the OSGi framework that the
MBeans are managing. Or there may be multiple MBean servers which
contain the MBeans defined in this specification. The introduction of
nested frameworks, such as those defined in RFC 138, may have their
management MBeans hosted in the MBeanServer which hosts the MBeans for
the outermost OSGi container. Alternatively, these MBeans may be
hosted, for example, in an application server's MBeanServer which is
embedding mulitple OSGi containers."
My interpretation of this is that the specification does not describe
how the MBeans are registered with an MBean server. So this JIRA seems
to go beyond what is required to implement the JMX specification.
This is not necessarily a problem, but it does make me wonder if doing
this work is in the scope of the original incubator proposal. I think
registration of MBeans with an MBeanServer is the responsibility of
the runtime into which Aries has been embedded rather than the aries
podling itself.
What do people think?
Alasdair
2009/10/21 Adam Wojtuniak (JIRA) <ji...@apache.org>:
> Implement JMX Agent
> -------------------
>
> Key: ARIES-29
> URL: https://issues.apache.org/jira/browse/ARIES-29
> Project: Aries
> Issue Type: New Feature
> Components: JMX
> Affects Versions: 1.0
> Reporter: Adam Wojtuniak
> Fix For: 1.0
>
>
> Implement JMX Agent. It should be responsible for tracking all MBean servers(registered as a services) and services which will be exposed as a Managed Beans (MBeans).
> JMX Agent should register following MBeans: Framework MBean, Bundle State MBean, Service State MBean, Package State MBean, Permission Admin MBean, Configuration Admin MBean,
> Provisioning Service MBean, User Admin MBean, Conditional Permission Admin MBean.
> It is open issue if we should track MBean servers registered as services but for now we can follow RI of JMX which listen to MBean Server services.
> For now we can track MBeanServers and when service is discovered register MBeans. Same in case when service is exposed as Managed MBeans it should be registered (on all available MBean servers) when is discovered.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
--
Alasdair Nottingham
alasdair.nottingham@gmail.com
Re: [jira] Commented: (ARIES-29) Implement JMX Agent
Posted by adam wojtuniak <ad...@gmail.com>.
Thanks Joe. I have one problem cause I created jira account with different
username than I proposed asf uid. For JIRA Iam
using adamwojtuniak but my apache account is still not created so I guess I
can change that. I will send another email to private-dev
for account request.
Best Regards,
Adam Wojtuniak
On Wed, Oct 21, 2009 at 11:07 PM, Joe Bohn <jo...@gmail.com> wrote:
> Adam,
>
> I just added you as an aries-developer so you should be able to assign the
> jira to yourself now. You may need to log-out then back in to jira.
>
> Joe
>
>
>
> Adam Wojtuniak (JIRA) wrote:
>
>> [
>> https://issues.apache.org/jira/browse/ARIES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768462#action_12768462]
>> Adam Wojtuniak commented on ARIES-29:
>> -------------------------------------
>>
>> If someone can assign this task to me I can start working on it . thanks.
>>
>> Implement JMX Agent
>>> -------------------
>>>
>>> Key: ARIES-29
>>> URL: https://issues.apache.org/jira/browse/ARIES-29
>>> Project: Aries
>>> Issue Type: New Feature
>>> Components: JMX
>>> Affects Versions: 1.0
>>> Reporter: Adam Wojtuniak
>>> Fix For: 1.0
>>>
>>>
>>> Implement JMX Agent. It should be responsible for tracking all MBean
>>> servers(registered as a services) and services which will be exposed as a
>>> Managed Beans (MBeans).
>>> JMX Agent should register following MBeans: Framework MBean, Bundle State
>>> MBean, Service State MBean, Package State MBean, Permission Admin MBean,
>>> Configuration Admin MBean,
>>> Provisioning Service MBean, User Admin MBean, Conditional Permission
>>> Admin MBean.
>>> It is open issue if we should track MBean servers registered as services
>>> but for now we can follow RI of JMX which listen to MBean Server services.
>>> For now we can track MBeanServers and when service is discovered register
>>> MBeans. Same in case when service is exposed as Managed MBeans it should be
>>> registered (on all available MBean servers) when is discovered.
>>>
>>
>>
Re: [jira] Commented: (ARIES-29) Implement JMX Agent
Posted by Alan Keane <al...@gmail.com>.
Great.. Thanks Joe
On Thu, Oct 22, 2009 at 1:28 PM, Joe Bohn <jo...@gmail.com> wrote:
> You're in.
>
> Joe
>
>
> Alan Keane wrote:
>
>> Hi Joe,
>> Could you do add me also?
>>
>> Cheers,
>> Alan
>>
>> On Wed, Oct 21, 2009 at 11:07 PM, Joe Bohn <jo...@gmail.com> wrote:
>>
>> Adam,
>>>
>>> I just added you as an aries-developer so you should be able to assign
>>> the
>>> jira to yourself now. You may need to log-out then back in to jira.
>>>
>>> Joe
>>>
>>>
>>>
>>> Adam Wojtuniak (JIRA) wrote:
>>>
>>> [
>>>>
>>>> https://issues.apache.org/jira/browse/ARIES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768462#action_12768462
>>>> ]
>>>> Adam Wojtuniak commented on ARIES-29:
>>>> -------------------------------------
>>>>
>>>> If someone can assign this task to me I can start working on it .
>>>> thanks.
>>>>
>>>> Implement JMX Agent
>>>>
>>>>> -------------------
>>>>>
>>>>> Key: ARIES-29
>>>>> URL: https://issues.apache.org/jira/browse/ARIES-29
>>>>> Project: Aries
>>>>> Issue Type: New Feature
>>>>> Components: JMX
>>>>> Affects Versions: 1.0
>>>>> Reporter: Adam Wojtuniak
>>>>> Fix For: 1.0
>>>>>
>>>>>
>>>>> Implement JMX Agent. It should be responsible for tracking all MBean
>>>>> servers(registered as a services) and services which will be exposed as
>>>>> a
>>>>> Managed Beans (MBeans).
>>>>> JMX Agent should register following MBeans: Framework MBean, Bundle
>>>>> State
>>>>> MBean, Service State MBean, Package State MBean, Permission Admin
>>>>> MBean,
>>>>> Configuration Admin MBean,
>>>>> Provisioning Service MBean, User Admin MBean, Conditional Permission
>>>>> Admin MBean.
>>>>> It is open issue if we should track MBean servers registered as
>>>>> services
>>>>> but for now we can follow RI of JMX which listen to MBean Server
>>>>> services.
>>>>> For now we can track MBeanServers and when service is discovered
>>>>> register
>>>>> MBeans. Same in case when service is exposed as Managed MBeans it
>>>>> should be
>>>>> registered (on all available MBean servers) when is discovered.
>>>>>
>>>>>
>>>>
>>
>
> --
> Joe
>
Re: [jira] Commented: (ARIES-29) Implement JMX Agent
Posted by Joe Bohn <jo...@gmail.com>.
You're in.
Joe
Alan Keane wrote:
> Hi Joe,
> Could you do add me also?
>
> Cheers,
> Alan
>
> On Wed, Oct 21, 2009 at 11:07 PM, Joe Bohn <jo...@gmail.com> wrote:
>
>> Adam,
>>
>> I just added you as an aries-developer so you should be able to assign the
>> jira to yourself now. You may need to log-out then back in to jira.
>>
>> Joe
>>
>>
>>
>> Adam Wojtuniak (JIRA) wrote:
>>
>>> [
>>> https://issues.apache.org/jira/browse/ARIES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768462#action_12768462]
>>> Adam Wojtuniak commented on ARIES-29:
>>> -------------------------------------
>>>
>>> If someone can assign this task to me I can start working on it . thanks.
>>>
>>> Implement JMX Agent
>>>> -------------------
>>>>
>>>> Key: ARIES-29
>>>> URL: https://issues.apache.org/jira/browse/ARIES-29
>>>> Project: Aries
>>>> Issue Type: New Feature
>>>> Components: JMX
>>>> Affects Versions: 1.0
>>>> Reporter: Adam Wojtuniak
>>>> Fix For: 1.0
>>>>
>>>>
>>>> Implement JMX Agent. It should be responsible for tracking all MBean
>>>> servers(registered as a services) and services which will be exposed as a
>>>> Managed Beans (MBeans).
>>>> JMX Agent should register following MBeans: Framework MBean, Bundle State
>>>> MBean, Service State MBean, Package State MBean, Permission Admin MBean,
>>>> Configuration Admin MBean,
>>>> Provisioning Service MBean, User Admin MBean, Conditional Permission
>>>> Admin MBean.
>>>> It is open issue if we should track MBean servers registered as services
>>>> but for now we can follow RI of JMX which listen to MBean Server services.
>>>> For now we can track MBeanServers and when service is discovered register
>>>> MBeans. Same in case when service is exposed as Managed MBeans it should be
>>>> registered (on all available MBean servers) when is discovered.
>>>>
>>>
>
--
Joe
Re: [jira] Commented: (ARIES-29) Implement JMX Agent
Posted by Alan Keane <al...@gmail.com>.
Hi Joe,
Could you do add me also?
Cheers,
Alan
On Wed, Oct 21, 2009 at 11:07 PM, Joe Bohn <jo...@gmail.com> wrote:
> Adam,
>
> I just added you as an aries-developer so you should be able to assign the
> jira to yourself now. You may need to log-out then back in to jira.
>
> Joe
>
>
>
> Adam Wojtuniak (JIRA) wrote:
>
>> [
>> https://issues.apache.org/jira/browse/ARIES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768462#action_12768462]
>> Adam Wojtuniak commented on ARIES-29:
>> -------------------------------------
>>
>> If someone can assign this task to me I can start working on it . thanks.
>>
>> Implement JMX Agent
>>> -------------------
>>>
>>> Key: ARIES-29
>>> URL: https://issues.apache.org/jira/browse/ARIES-29
>>> Project: Aries
>>> Issue Type: New Feature
>>> Components: JMX
>>> Affects Versions: 1.0
>>> Reporter: Adam Wojtuniak
>>> Fix For: 1.0
>>>
>>>
>>> Implement JMX Agent. It should be responsible for tracking all MBean
>>> servers(registered as a services) and services which will be exposed as a
>>> Managed Beans (MBeans).
>>> JMX Agent should register following MBeans: Framework MBean, Bundle State
>>> MBean, Service State MBean, Package State MBean, Permission Admin MBean,
>>> Configuration Admin MBean,
>>> Provisioning Service MBean, User Admin MBean, Conditional Permission
>>> Admin MBean.
>>> It is open issue if we should track MBean servers registered as services
>>> but for now we can follow RI of JMX which listen to MBean Server services.
>>> For now we can track MBeanServers and when service is discovered register
>>> MBeans. Same in case when service is exposed as Managed MBeans it should be
>>> registered (on all available MBean servers) when is discovered.
>>>
>>
>>
Re: [jira] Commented: (ARIES-29) Implement JMX Agent
Posted by Joe Bohn <jo...@gmail.com>.
Adam,
I just added you as an aries-developer so you should be able to assign
the jira to yourself now. You may need to log-out then back in to jira.
Joe
Adam Wojtuniak (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/ARIES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768462#action_12768462 ]
>
> Adam Wojtuniak commented on ARIES-29:
> -------------------------------------
>
> If someone can assign this task to me I can start working on it . thanks.
>
>> Implement JMX Agent
>> -------------------
>>
>> Key: ARIES-29
>> URL: https://issues.apache.org/jira/browse/ARIES-29
>> Project: Aries
>> Issue Type: New Feature
>> Components: JMX
>> Affects Versions: 1.0
>> Reporter: Adam Wojtuniak
>> Fix For: 1.0
>>
>>
>> Implement JMX Agent. It should be responsible for tracking all MBean servers(registered as a services) and services which will be exposed as a Managed Beans (MBeans).
>> JMX Agent should register following MBeans: Framework MBean, Bundle State MBean, Service State MBean, Package State MBean, Permission Admin MBean, Configuration Admin MBean,
>> Provisioning Service MBean, User Admin MBean, Conditional Permission Admin MBean.
>> It is open issue if we should track MBean servers registered as services but for now we can follow RI of JMX which listen to MBean Server services.
>> For now we can track MBeanServers and when service is discovered register MBeans. Same in case when service is exposed as Managed MBeans it should be registered (on all available MBean servers) when is discovered.
>
[jira] Commented: (ARIES-29) Implement JMX Agent
Posted by "Adam Wojtuniak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768462#action_12768462 ]
Adam Wojtuniak commented on ARIES-29:
-------------------------------------
If someone can assign this task to me I can start working on it . thanks.
> Implement JMX Agent
> -------------------
>
> Key: ARIES-29
> URL: https://issues.apache.org/jira/browse/ARIES-29
> Project: Aries
> Issue Type: New Feature
> Components: JMX
> Affects Versions: 1.0
> Reporter: Adam Wojtuniak
> Fix For: 1.0
>
>
> Implement JMX Agent. It should be responsible for tracking all MBean servers(registered as a services) and services which will be exposed as a Managed Beans (MBeans).
> JMX Agent should register following MBeans: Framework MBean, Bundle State MBean, Service State MBean, Package State MBean, Permission Admin MBean, Configuration Admin MBean,
> Provisioning Service MBean, User Admin MBean, Conditional Permission Admin MBean.
> It is open issue if we should track MBean servers registered as services but for now we can follow RI of JMX which listen to MBean Server services.
> For now we can track MBeanServers and when service is discovered register MBeans. Same in case when service is exposed as Managed MBeans it should be registered (on all available MBean servers) when is discovered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ARIES-29) Implement JMX Agent
Posted by "Adam Wojtuniak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Wojtuniak reassigned ARIES-29:
-----------------------------------
Assignee: Adam Wojtuniak
> Implement JMX Agent
> -------------------
>
> Key: ARIES-29
> URL: https://issues.apache.org/jira/browse/ARIES-29
> Project: Aries
> Issue Type: New Feature
> Components: JMX
> Affects Versions: 1.0
> Reporter: Adam Wojtuniak
> Assignee: Adam Wojtuniak
> Fix For: 1.0
>
>
> Implement JMX Agent. It should be responsible for tracking all MBean servers(registered as a services) and services which will be exposed as a Managed Beans (MBeans).
> JMX Agent should register following MBeans: Framework MBean, Bundle State MBean, Service State MBean, Package State MBean, Permission Admin MBean, Configuration Admin MBean,
> Provisioning Service MBean, User Admin MBean, Conditional Permission Admin MBean.
> It is open issue if we should track MBean servers registered as services but for now we can follow RI of JMX which listen to MBean Server services.
> For now we can track MBeanServers and when service is discovered register MBeans. Same in case when service is exposed as Managed MBeans it should be registered (on all available MBean servers) when is discovered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ARIES-29) Implement JMX Agent
Posted by "Adam Wojtuniak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Wojtuniak resolved ARIES-29.
---------------------------------
Resolution: Fixed
> Implement JMX Agent
> -------------------
>
> Key: ARIES-29
> URL: https://issues.apache.org/jira/browse/ARIES-29
> Project: Aries
> Issue Type: New Feature
> Components: JMX
> Affects Versions: 1.0
> Reporter: Adam Wojtuniak
> Assignee: Adam Wojtuniak
> Fix For: 1.0
>
>
> Implement JMX Agent. It should be responsible for tracking all MBean servers(registered as a services) and services which will be exposed as a Managed Beans (MBeans).
> JMX Agent should register following MBeans: Framework MBean, Bundle State MBean, Service State MBean, Package State MBean, Permission Admin MBean, Configuration Admin MBean,
> Provisioning Service MBean, User Admin MBean, Conditional Permission Admin MBean.
> It is open issue if we should track MBean servers registered as services but for now we can follow RI of JMX which listen to MBean Server services.
> For now we can track MBeanServers and when service is discovered register MBeans. Same in case when service is exposed as Managed MBeans it should be registered (on all available MBean servers) when is discovered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ARIES-29) Implement JMX Agent
Posted by "Jeremy Hughes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hughes updated ARIES-29:
-------------------------------
Fix Version/s: (was: 1.0)
0.1
> Implement JMX Agent
> -------------------
>
> Key: ARIES-29
> URL: https://issues.apache.org/jira/browse/ARIES-29
> Project: Aries
> Issue Type: New Feature
> Components: JMX
> Affects Versions: 1.0
> Reporter: Adam Wojtuniak
> Assignee: Adam Wojtuniak
> Fix For: 0.1
>
>
> Implement JMX Agent. It should be responsible for tracking all MBean servers(registered as a services) and services which will be exposed as a Managed Beans (MBeans).
> JMX Agent should register following MBeans: Framework MBean, Bundle State MBean, Service State MBean, Package State MBean, Permission Admin MBean, Configuration Admin MBean,
> Provisioning Service MBean, User Admin MBean, Conditional Permission Admin MBean.
> It is open issue if we should track MBean servers registered as services but for now we can follow RI of JMX which listen to MBean Server services.
> For now we can track MBeanServers and when service is discovered register MBeans. Same in case when service is exposed as Managed MBeans it should be registered (on all available MBean servers) when is discovered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (ARIES-29) Implement JMX Agent
Posted by "Adam Wojtuniak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on ARIES-29 started by Adam Wojtuniak.
> Implement JMX Agent
> -------------------
>
> Key: ARIES-29
> URL: https://issues.apache.org/jira/browse/ARIES-29
> Project: Aries
> Issue Type: New Feature
> Components: JMX
> Affects Versions: 1.0
> Reporter: Adam Wojtuniak
> Assignee: Adam Wojtuniak
> Fix For: 1.0
>
>
> Implement JMX Agent. It should be responsible for tracking all MBean servers(registered as a services) and services which will be exposed as a Managed Beans (MBeans).
> JMX Agent should register following MBeans: Framework MBean, Bundle State MBean, Service State MBean, Package State MBean, Permission Admin MBean, Configuration Admin MBean,
> Provisioning Service MBean, User Admin MBean, Conditional Permission Admin MBean.
> It is open issue if we should track MBean servers registered as services but for now we can follow RI of JMX which listen to MBean Server services.
> For now we can track MBeanServers and when service is discovered register MBeans. Same in case when service is exposed as Managed MBeans it should be registered (on all available MBean servers) when is discovered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.