Wildfly 9.0.0.Final: Mod-Cluster configuration issue with custom-load-metric
rbattenfeld Jul 23, 2015 4:03 AMHi
We try to migrate from Wildfly 8.2.0.Final to Wildfly 9.0.0.Final. We face an error when we deploy our apps. With 8.2.0, it works fine. We have to use a custom load metric so that mod-cluster routes is able as we need.
We get this stack trace:
09:50:55,349 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 49) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]): java.lang.NoClassDefFoundError: org/jboss/util/propertyeditor/PropertyEditors
at org.wildfly.extension.mod_cluster.ModClusterSubsystemAdd.addLoadMetrics(ModClusterSubsystemAdd.java:352)
at org.wildfly.extension.mod_cluster.ModClusterSubsystemAdd.getModClusterLoadProvider(ModClusterSubsystemAdd.java:292)
at org.wildfly.extension.mod_cluster.ModClusterSubsystemAdd.performBoottime(ModClusterSubsystemAdd.java:124)
at org.jboss.as.controller.AbstractBoottimeAddStepHandler.performBoottime(AbstractBoottimeAddStepHandler.java:153)
at org.jboss.as.controller.AbstractBoottimeAddStepHandler.performRuntime(AbstractBoottimeAddStepHandler.java:112)
at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:128)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:803)
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:601)
at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330)
at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:356)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.lang.ClassNotFoundException: org.jboss.util.propertyeditor.PropertyEditors from [Module "org.wildfly.extension.mod_cluster:main" from local module loader @57536d79 (finder: local module finder @3b0143d3 (roots: C:\develop\DevTools\wildfly-9.0.0.Final\modules,C:\develop\DevTools\wildfly-9.0.0.Final\modules\system\layers\base))]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
... 15 more
The configuration looks like this:
<subsystem xmlns="urn:jboss:domain:modcluster:2.0">
<mod-cluster-config advertise-socket="modcluster" connector="ajp">
<dynamic-load-provider>
<custom-load-metric class="org.jboss.modcluster.load.metric.impl.MBeanAttributeLoadMetric" capacity="5.0">
<property name="pattern" value="com.six_group.ssx.seni.request_portal.metrics:service=InitialDownloadResult"/>
<property name="attribute" value="CurrentRequestCount"/>
</custom-load-metric>
<!-- load-metric type="cpu"/ -->
</dynamic-load-provider>
</mod-cluster-config>
</subsystem>
Do we have to change the configuration?
Regards,
Ralf