-
1. Re: JON integration what to do?
timfox Jan 18, 2010 1:54 PM (in response to clebert.suconic)I do know that infinispan recently enabled JON support for them.
Apparently this was very simple, they didn't need any config - JON just picked up the mbeans direct.
-
2. Re: JON integration what to do?
timfox Jan 18, 2010 1:55 PM (in response to timfox)... or was that JOPR?
http://infinispan.blogspot.com/2009/12/new-video-demo-monitoring-infinispan.html
Hell, now I have confused myself. Not sure if JOPR and JON are the same thing or not.
??
-
3. Re: JON integration what to do?
timfox Jan 18, 2010 2:00 PM (in response to timfox)I have to say JOPR, JON and RHX must win the prize for the worst names projects.
Completely unmemorable. May as well be called yqwtqytw, isjiajsd, and iqdjqojsq
-
4. Re: JON integration what to do?
timfox Jan 18, 2010 2:07 PM (in response to timfox)Here's how they did it:
http://community.jboss.org/wiki/MonitoringInfinispanwithJOPR
And here is the JOPR wiki, so yes, it does seem there are docs:
-
5. Re: JON integration what to do?
clebert.suconic Jan 18, 2010 2:11 PM (in response to timfox)@Tim: I was looking at how to integrate hornetq on AS6, and at JON on AS6.
There's another JIRA to integrate the console at standalone for later. We may reuse some of this work... but I guess that's a separate task.
(Just to narrow the scope on what's being done now)
-
6. Re: JON integration what to do?
shelly.mcgowan Jan 18, 2010 2:15 PM (in response to clebert.suconic)
Is that what you were interested in? -
7. Re: JON integration what to do?
clebert.suconic Jan 18, 2010 2:28 PM (in response to shelly.mcgowan)So, everything that's done on the console for messaging integration is creating and removing destination? -
8. Re: JON integration what to do?
clebert.suconic Jan 18, 2010 2:28 PM (in response to clebert.suconic)Besides that.. I believe that all the JMX operations are still exposed through JON, right? -
9. Re: JON integration what to do?
timfox Jan 18, 2010 2:32 PM (in response to clebert.suconic)According to the infinispan guys, they didn't have to write a plugin at all.
Apparently JON now can deal with MBeans directly without any kind of plugin (?)
Perhaps one of the JON/JOPR people could comment, as I know next to nothing about this stuff
-
10. Re: JON integration what to do?
clebert.suconic Jan 18, 2010 2:35 PM (in response to timfox)I *believe* there is a GUI for creating and dropping destinations. I couldn't confirm that as the console is not working ATM. -
11. Re: JON integration what to do?
brian.stansberry Jan 18, 2010 3:45 PM (in response to clebert.suconic)The plugin definition that tells JOPR how to handle JBM is part of the JBoss AS 5 plugin found at https://svn.jboss.org/repos/jopr/trunk/modules/plugins/jboss-as-5/src/main/resources/META-INF/rhq-plugin.xml. There is further code in the https://svn.jboss.org/repos/jopr/trunk/modules/plugins/jboss-as-5/src/main/java/org/rhq/plugins/jbossas5/ package.
That paragraph exhausts my detail knowledge of how the plugin works on the client side. (The server side I understand much better.) A couple points jump out though:
1) The JBM-related stuff is bundled together with a bunch of other AS 5 stuff. It's not an independent piece.
2) The whole thing is the jbossas5 plugin. I doubt the move to HornetQ will be the only significant incompatible difference in AS 6, which implies the JOPR folks will need a jbossas6 plugin soon. I'll be having a discussion tomorrow with Charles Crouch from the JOPR side and Shelly McGowan from the AS side about getting the JOPR-based embedded console working again. I'll clarify there Charles' plans about differentiated AS 5/6.
All of this is detail though pointing to a larger issue. Are JBoss AS, EAP and projects/products that consume those the only places where our JOPR-based tools (incl JON) are going to need to manage HornetQ instances? If not we should come up with an overall strategy for how the management will work across all the use cases. I'll make sure the relevant people are aware of this thread.
-
12. Re: JON integration what to do?
brian.stansberry Jan 18, 2010 3:46 PM (in response to clebert.suconic)Yes, there is a GUI interface for creating/dropping destinations. You can see it in AS 6.0.0.M1. It should be restored to AS trunk w/in a few days. -
13. Re: JON integration what to do?
brian.stansberry Jan 18, 2010 5:28 PM (in response to clebert.suconic)clebert.suconic@jboss.com wrote:
clebert.suconic@jboss.com wrote:
Besides creating and removing destinations, you can also see the metrics on the JBM destinations, change configuration values plus perform various control operations (start/stop, list messages, remove all messages.) All of this stuff isn't done via JMX; the AS exposes it all via the ProfileService ManagmentObject (@ManagedObject etc) stuff in the AS's messaging module.
JOPR plugins can also be written against JMX interfaces. What the ProfileService ManagementObject stuff brings is the ability to persist configuration changes made via the console and reapply them on server restart. Tim has pointed out that HornetQ already persists any relevant state changes in its journal.
I imagine the JOPR folks have their own thoughts on how they want to manage stuff; their input is needed. Writing a ProfileService ManagementObject layer like there is for JBM shouldn't be a big deal (I've said I and Emanuel can do much of the grunt work) but lets talk to the JOPR folks first.
-
14. Re: JON integration what to do?
brian.stansberry Jan 18, 2010 5:29 PM (in response to brian.stansberry)BTW, the @ManagedObject stuff for JBM also exposes a lot of configuration values for the ServerPeer, but looking at the console I don't see that's actually exposed in the GUI.