[xwiki-devs] [Proposal] Use JMX for XWiki Management + xwiki-management module in platform/core
Hi devs, We need to introduce some ways to manage XE instances by exposing management data and operations. For example exposing the content of the xwiki caches, operation to flush them, etc. Even the ability to view/modify XWiki's configuration data at runtime. I propose to use a standard to do this: JMX. The concept is easy: - you write a MBean java bean - you register it against an MBean server Note that all containers support JMX. I've tried it with Jetty and it's enabled by default which means that you can try it by starting XWiki with jetty then open another shell and type "jconsole" (it's part of the JDK since 1.5). JConsole is a JMX console. Then go to the MBeans tab and you'll Mbeans already registered. You'll see for example the JBoss caches since JBoss Caches exposes some MBeans by default. I have written a POC already in the Velocity module to expose the velocity engines, the template namespaces and the macros registered in each template. I'm ready to commit it as a first step in the direction of using JMX. I'd also like to introduce a xwiki-management module which will contain some generic code related to JMX management. Right now I have a JMXBeanRegistration component to perform registration of XWiki MBean. That component will be used by any module wanting to register a MBean. WDYT? Thanks -Vincent
On Mon, Jun 14, 2010 at 12:59, Vincent Massol <[email protected]> wrote:
Hi devs,
We need to introduce some ways to manage XE instances by exposing management data and operations. For example exposing the content of the xwiki caches, operation to flush them, etc. Even the ability to view/modify XWiki's configuration data at runtime.
I propose to use a standard to do this: JMX.
The concept is easy: - you write a MBean java bean - you register it against an MBean server
Note that all containers support JMX. I've tried it with Jetty and it's enabled by default which means that you can try it by starting XWiki with jetty then open another shell and type "jconsole" (it's part of the JDK since 1.5). JConsole is a JMX console. Then go to the MBeans tab and you'll Mbeans already registered. You'll see for example the JBoss caches since JBoss Caches exposes some MBeans by default.
I have written a POC already in the Velocity module to expose the velocity engines, the template namespaces and the macros registered in each template.
I'm ready to commit it as a first step in the direction of using JMX.
I'd also like to introduce a xwiki-management module which will contain some generic code related to JMX management. Right now I have a JMXBeanRegistration component to perform registration of XWiki MBean. That component will be used by any module wanting to register a MBean.
WDYT?
+1 for starting using JMX "xwiki-management" sounds a bit too generic if it's only about JMX
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Jun 14, 2010, at 2:06 PM, Thomas Mortagne wrote:
On Mon, Jun 14, 2010 at 12:59, Vincent Massol <[email protected]> wrote:
Hi devs,
We need to introduce some ways to manage XE instances by exposing management data and operations. For example exposing the content of the xwiki caches, operation to flush them, etc. Even the ability to view/modify XWiki's configuration data at runtime.
I propose to use a standard to do this: JMX.
The concept is easy: - you write a MBean java bean - you register it against an MBean server
Note that all containers support JMX. I've tried it with Jetty and it's enabled by default which means that you can try it by starting XWiki with jetty then open another shell and type "jconsole" (it's part of the JDK since 1.5). JConsole is a JMX console. Then go to the MBeans tab and you'll Mbeans already registered. You'll see for example the JBoss caches since JBoss Caches exposes some MBeans by default.
I have written a POC already in the Velocity module to expose the velocity engines, the template namespaces and the macros registered in each template.
I'm ready to commit it as a first step in the direction of using JMX.
I'd also like to introduce a xwiki-management module which will contain some generic code related to JMX management. Right now I have a JMXBeanRegistration component to perform registration of XWiki MBean. That component will be used by any module wanting to register a MBean.
WDYT?
+1 for starting using JMX
"xwiki-management" sounds a bit too generic if it's only about JMX
The domain is management. It happens that the technology used is JMX for now but this could change. I prefer a name by domain than by technology. Thanks -Vincent
On Mon, Jun 14, 2010 at 14:19, Vincent Massol <[email protected]> wrote:
On Jun 14, 2010, at 2:06 PM, Thomas Mortagne wrote:
On Mon, Jun 14, 2010 at 12:59, Vincent Massol <[email protected]> wrote:
Hi devs,
We need to introduce some ways to manage XE instances by exposing management data and operations. For example exposing the content of the xwiki caches, operation to flush them, etc. Even the ability to view/modify XWiki's configuration data at runtime.
I propose to use a standard to do this: JMX.
The concept is easy: - you write a MBean java bean - you register it against an MBean server
Note that all containers support JMX. I've tried it with Jetty and it's enabled by default which means that you can try it by starting XWiki with jetty then open another shell and type "jconsole" (it's part of the JDK since 1.5). JConsole is a JMX console. Then go to the MBeans tab and you'll Mbeans already registered. You'll see for example the JBoss caches since JBoss Caches exposes some MBeans by default.
I have written a POC already in the Velocity module to expose the velocity engines, the template namespaces and the macros registered in each template.
I'm ready to commit it as a first step in the direction of using JMX.
I'd also like to introduce a xwiki-management module which will contain some generic code related to JMX management. Right now I have a JMXBeanRegistration component to perform registration of XWiki MBean. That component will be used by any module wanting to register a MBean.
WDYT?
+1 for starting using JMX
"xwiki-management" sounds a bit too generic if it's only about JMX
The domain is management. It happens that the technology used is JMX for now but this could change. I prefer a name by domain than by technology.
Ok
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
+1, JV. On Mon, Jun 14, 2010 at 12:59 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
We need to introduce some ways to manage XE instances by exposing management data and operations. For example exposing the content of the xwiki caches, operation to flush them, etc. Even the ability to view/modify XWiki's configuration data at runtime.
I propose to use a standard to do this: JMX.
The concept is easy: - you write a MBean java bean - you register it against an MBean server
Note that all containers support JMX. I've tried it with Jetty and it's enabled by default which means that you can try it by starting XWiki with jetty then open another shell and type "jconsole" (it's part of the JDK since 1.5). JConsole is a JMX console. Then go to the MBeans tab and you'll Mbeans already registered. You'll see for example the JBoss caches since JBoss Caches exposes some MBeans by default.
I have written a POC already in the Velocity module to expose the velocity engines, the template namespaces and the macros registered in each template.
I'm ready to commit it as a first step in the direction of using JMX.
I'd also like to introduce a xwiki-management module which will contain some generic code related to JMX management. Right now I have a JMXBeanRegistration component to perform registration of XWiki MBean. That component will be used by any module wanting to register a MBean.
WDYT?
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 Thanks, Marius On 06/14/2010 01:59 PM, Vincent Massol wrote:
Hi devs,
We need to introduce some ways to manage XE instances by exposing management data and operations. For example exposing the content of the xwiki caches, operation to flush them, etc. Even the ability to view/modify XWiki's configuration data at runtime.
I propose to use a standard to do this: JMX.
The concept is easy: - you write a MBean java bean - you register it against an MBean server
Note that all containers support JMX. I've tried it with Jetty and it's enabled by default which means that you can try it by starting XWiki with jetty then open another shell and type "jconsole" (it's part of the JDK since 1.5). JConsole is a JMX console. Then go to the MBeans tab and you'll Mbeans already registered. You'll see for example the JBoss caches since JBoss Caches exposes some MBeans by default.
I have written a POC already in the Velocity module to expose the velocity engines, the template namespaces and the macros registered in each template.
I'm ready to commit it as a first step in the direction of using JMX.
I'd also like to introduce a xwiki-management module which will contain some generic code related to JMX management. Right now I have a JMXBeanRegistration component to perform registration of XWiki MBean. That component will be used by any module wanting to register a MBean.
WDYT?
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (4)
-
Jean-Vincent Drean -
Marius Dumitru Florea -
Thomas Mortagne -
Vincent Massol