如何在 WildFly10 中升级 org.jboss.as.jmx:main
how to get upgraded org.jboss.as.jmx:main in WildFly10
我正在尝试将我的应用程序从 JBoss 7 升级到 WildFly10,但我收到警告:
[0m[33m13:53:36,641 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6)
WFLYSRV0018: Deployment "deployment.mywar.war" is using a private module
("org.jboss.as.jmx:main") which may be changed or removed in future versions
without notice.
模块在jboss-deployment-structure.xml
中提到如下:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure >
<deployment>
<dependencies>
<module name="org.jboss.as.jmx"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
jmx 的新模块是如何调用的?我试图用 org.jboss.remoting-jmx
替换它,但后来我得到了
Invocation of init method failed;
nested exception is javax.management.JMRuntimeException:
Failed to load MBeanServerBuilder class org.jboss.as.jmx.PluggableMBeanServerBuilder:
java.lang.ClassNotFoundException: org.jboss.as.jmx.PluggableMBeanServerBuilder
根据 WildFly 论坛,它没有任何意义,请参阅引用 (source)
You got warning message as you are using internal "non-public" modules
from application server. Which just tells you that you should be
careful with this.
我正在尝试将我的应用程序从 JBoss 7 升级到 WildFly10,但我收到警告:
[0m[33m13:53:36,641 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6)
WFLYSRV0018: Deployment "deployment.mywar.war" is using a private module
("org.jboss.as.jmx:main") which may be changed or removed in future versions
without notice.
模块在jboss-deployment-structure.xml
中提到如下:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure >
<deployment>
<dependencies>
<module name="org.jboss.as.jmx"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
jmx 的新模块是如何调用的?我试图用 org.jboss.remoting-jmx
替换它,但后来我得到了
Invocation of init method failed;
nested exception is javax.management.JMRuntimeException:
Failed to load MBeanServerBuilder class org.jboss.as.jmx.PluggableMBeanServerBuilder:
java.lang.ClassNotFoundException: org.jboss.as.jmx.PluggableMBeanServerBuilder
根据 WildFly 论坛,它没有任何意义,请参阅引用 (source)
You got warning message as you are using internal "non-public" modules from application server. Which just tells you that you should be careful with this.