简体   繁体   English

JBoss 7.1.x不会在Fedora 18中启动

[英]JBoss 7.1.x wont start in Fedora 18

Here is a problem - JBoss throws the following an error at startup : 这是一个问题-JBoss在启动时引发以下错误:

Exception in thread "main" java.lang.ExceptionInInitializerError
    at org.jboss.as.server.Main.main(Main.java:73)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at org.jboss.modules.Module.run(Module.java:260)
    at org.jboss.modules.Main.main(Main.java:291)
Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
    at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
    at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)

this is an old issue and i believe was fixed here a while ago. 这是一个老问题,我相信这是固定在这里前一段时间。 The difference here that i do not have jmx parameters at startup. 区别在于我在启动时没有jmx参数。

The things I've been noticed: 我注意到的东西:

  • same error pops up in both Oracle's and OpenJDK jdk Oracle和OpenJDK jdk中都弹出相同的错误
  • adding parameter -Djava.util.logging.manager=org.jboss.logmanager.LogManager to the /bin/standalone.conf as suggested here just generates the same error (not ClassNotFound as should be expected) 添加参数-Djava.util.logging.manager = org.jboss.logmanager.LogManager到/bin/standalone.conf所建议这里只是生成相同的错误(未ClassNotFound的作为应该预计)
  • i also tried to move jboss-logmanager-xxx.jar to /bin directory but no luck 我也尝试将jboss-logmanager-xxx.jar移到/ bin目录,但是没有运气

Any ideas? 有任何想法吗?

当我返回到Oracle的JDK并以替代方式更改了这个新的jdk时,问题得到了解决。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM