<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'><br><br><hr id="zwchr"><blockquote id="DWT5004" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Brian Stansberry" <brian.stansberry@redhat.com><br><b>To: </b>jboss-as7-dev@lists.jboss.org<br><b>Sent: </b>Friday, August 19, 2011 11:52:40 AM<br><b>Subject: </b>Re: [jboss-as7-dev] JMX [was: Dear subsystem owners/components leads ....]<br><br>What kind of extensibility are you thinking about?<br><br>I have no objection at all to the kind of simple JMX gateway resource <br>David describes. If someone in the community wants to contribute that, <br>that would be great.<br><br>I would object to it though if its presence became an excuse for <br>subsystems not exposing their full management API via the standard <br>management model. ;)<br></blockquote>That's exactly the slippery slope I don't want us to go down! From an Andiamo perspective, we need ONE management layer that handles everything.<br><br>Let's keep this on track.<br><br>Andy<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><br>On 8/19/11 12:02 PM, Eduardo Martins wrote:<br>> The JMX exposure in CLI and Web Console can be basic, like I<br>> mentioned, but should be easy extendable, so the community may enhance<br>> it, if there is interest...<br>><br>> -- Eduardo<br>> ..............................................<br>> http://emmartins.blogspot.com<br>> http://redhat.com/solutions/telco<br>><br>> On Fri, Aug 19, 2011 at 5:52 PM, David M. Lloyd<david.lloyd@redhat.com> wrote:<br>>> What Brian is saying is that we will not map arbitrary JMX objects to<br>>> the management mode.<br>>><br>>> I think it might make sense though - eventually - to have a JMX resource<br>>> which has operations for calling into JMX (for open mbean types only of<br>>> course). Note that this would NOT be a mapping, just a single<br>>> management resource which is a gateway to JMX, and apart from accessing<br>>> attributes and invoking operations, no other JMX functions would be<br>>> supported (in particular, notifications).<br>>><br>>> On 08/19/2011 11:29 AM, Eduardo Martins wrote:<br>>>> It was and still is my biggest complain with AS7, the support for the<br>>>> official java management spec is ... zero!<br>>>><br>>>> IMHO the CLI should have an easy way to invoke a JMX operation,<br>>>> whatever the MBean, how hard can it be when previous AS releases had<br>>>> twiddle? And the JMX subsystem should have a module in the management<br>>>> console, providing access to the MBeans in the JVM MBean server,<br>>>> relying on JConsole is not good nowadays, not all OSes have it, again<br>>>> we already had such tool...<br>>>><br>>>> -- Eduardo<br>>>> ..............................................<br>>>> http://emmartins.blogspot.com<br>>>> http://redhat.com/solutions/telco<br>>>><br>>>><br>>>><br>>>> On Fri, Aug 19, 2011 at 4:35 PM,<ssilvert@redhat.com> wrote:<br>>>>> Quoting Scott Marlow<smarlow@redhat.com>:<br>>>>>> Heiko,<br>>>>>><br>>>>>> Some of the JPA persistence providers support JMX for administrative<br>>>>>> operations (Hibernate statistics for example). Do we have any magic way<br>>>>>> to get JMX MBeans into the management console? Probably will need to be<br>>>>>> dynamic based on deployment time processing.<br>>>>>><br>>>>>> Thanks,<br>>>>>> Scott<br>>>>><br>>>>> Scott,<br>>>>><br>>>>> Heiko is out for the rest of this month, so I'm not sure if he will be<br>>>>> able to answer.<br>>>>><br>>>>> Off hand, I don't think we currently have an easy way to directly<br>>>>> access JMX from the console. There would be a lot of low level<br>>>>> transport stuff to deal with that we've already worked through for the<br>>>>> management API. I doubt that we would want to go and build a<br>>>>> transport layer for JMX as well.<br>>>>><br>>>>> I think the better question is can we (should we) expose JMX through<br>>>>> the management API? If so it would be accessible from both the<br>>>>> console and the CLI.<br>>>>><br>>>>> Does anyone have thoughts about this?<br>>>>><br>>>>> Stan<br>>>>><br>>>>><br>>>>><br>>>>> _______________________________________________<br>>>>> jboss-as7-dev mailing list<br>>>>> jboss-as7-dev@lists.jboss.org<br>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev<br>>>>><br>>>><br>>>> _______________________________________________<br>>>> jboss-as7-dev mailing list<br>>>> jboss-as7-dev@lists.jboss.org<br>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev<br>>><br>>><br>>> --<br>>> - DML<br>>> _______________________________________________<br>>> jboss-as7-dev mailing list<br>>> jboss-as7-dev@lists.jboss.org<br>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev<br>>><br>><br>> _______________________________________________<br>> jboss-as7-dev mailing list<br>> jboss-as7-dev@lists.jboss.org<br>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev<br><br><br>-- <br>Brian Stansberry<br>Principal Software Engineer<br>JBoss by Red Hat<br>_______________________________________________<br>jboss-as7-dev mailing list<br>jboss-as7-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/jboss-as7-dev<br></blockquote><br></div></body></html>