Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dgervalle1 +XWiki.evalica - Content
-
... ... @@ -13,7 +13,7 @@ 13 13 ** (starting with XE 3.1) Monitor the Logback Logging configuration and change it 14 14 15 15 {{info}} 16 -XWiki also has a [[Monitor Plugin>>Documentation .AdminGuide.Logging||anchor="HActivatingtheXWikiMonitoringfeature"]] that you can use to monitor execution times. However this plugin is going to be deprecated in the future and replaced by the JMX technology.16 +XWiki also has a [[Monitor Plugin>>DocumentationAdminGuide.Logging||anchor="HActivatingtheXWikiMonitoringfeature"]] that you can use to monitor execution times. However this plugin is going to be deprecated in the future and replaced by the JMX technology. 17 17 {{/info}} 18 18 19 19 = JavaMelody = ... ... @@ -62,38 +62,6 @@ 62 62 63 63 Then restart XWiki and access JavaMelody at ##http:~/~/localhost:8080/xwiki/monitoring##. 64 64 65 -{{warning}} 66 -Recent versions of JavaMelody (at least 1.70+ ?) require the configuration in this guide to be adapted like this: 67 - 68 -{{code}} 69 -in web.xml: 70 ------------ 71 - 72 -<filter> 73 - <filter-name>javamelody</filter-name> 74 - <filter-class>net.bull.javamelody.MonitoringFilter</filter-class> 75 - <async-supported>true</async-supported> 76 -</filter> 77 -<filter-mapping> 78 - <filter-name>javamelody</filter-name> 79 - <url-pattern>/*</url-pattern> 80 - <dispatcher>REQUEST</dispatcher> 81 - <dispatcher>ASYNC</dispatcher> 82 -</filter-mapping> 83 -<listener> 84 - <listener-class>net.bull.javamelody.SessionListener</listener-class> 85 -</listener> 86 - 87 - 88 - 89 -in hibernate.cfg.xml: 90 ---------------------- 91 - 92 -<property name="connection.driver_class">net.bull.javamelody.JdbcDriver</property> 93 -<property name="connection.driver">com.mysql.jdbc.Driver</property> 94 -{{/code}} 95 -{{/warning}} 96 - 97 97 = JMX Console = 98 98 99 99 Since JMX is a standard you can use [[any JMX-compatible monitoring console>>http://stackoverflow.com/questions/1744900/what-is-the-best-or-most-commonly-used-jmx-console-client]] (most application servers provide a web-based JMX console). There's also a console called [[JConsole>>http://docs.oracle.com/javase/7/docs/technotes/guides/management/jconsole.html]] which is bundled by default in the Java Runtime you're using. To start it, simply execute the ##jconsole## executable.