JBoss AS 7 configuration should not be needed

[GoogleCodeExporter]

What steps will reproduce the problem?
1. When deploying a webapp including javamelody in JBoss AS 7 and without 
configuration of modules, the following stack-trace is printed and the 
deployment of the webapp fails:

WARN  [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC0000
4: Failure during stop of service jboss.web.deployment.default-host./test: 
java.lang.NoClassDefFoundError: com/sun/management/OperatingSystemMXBean
        at net.bull.javamelody.MemoryInformations.<init>(MemoryInformations.java:75)
        at net.bull.javamelody.JavaInformations.<init>(JavaInformations.java:140)
        at net.bull.javamelody.HtmlController.writeHtmlToLastShutdownFile(HtmlController.java:297)
        at net.bull.javamelody.MonitoringController.writeHtmlToLastShutdownFile(MonitoringController.java:248)
        at net.bull.javamelody.FilterContext.destroy(FilterContext.java:288)
        at net.bull.javamelody.MonitoringFilter.destroy(MonitoringFilter.java:141)
        at org.apache.catalina.core.ApplicationFilterConfig.release(ApplicationFilterConfig.java:504)
        at org.apache.catalina.core.StandardContext.filterStop(StandardContext.java:3277)
        at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3960)
        at org.jboss.as.web.deployment.WebDeploymentService.stop(WebDeploymentService.java:86)
        at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1909)
        at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1872)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

There is documentation to configure JBoss AS 7 and to make it work here:
https://code.google.com/p/javamelody/wiki/UserGuideAdvanced#Usage_of_in_JBoss_AS
_7_%28which_uses_OSGI%29

It is expected that it works without needing JBoss AS 7 configuration.

Original issue reported on code.google.com by evernat@free.fr on 2 Mar 2013 at 6:38

[GoogleCodeExporter]

It is fixed: configuration of JBoss AS 7 modules is not needed anymore.
It is committed in trunk (revision 3297) and ready for the next release (1.44)

Original comment by evernat@free.fr on 2 Mar 2013 at 6:46

• Changed state: Fixed
• Added labels: Type-Enhancement
• Removed labels: Type-Defect