3 Replies Latest reply on Feb 6, 2013 9:14 AM by miguelius

    jboss as 7 doesn't start logmanager is back

    miguelius
    miguelius Feb 6, 2013 7:44 AM

      Hi!

       

      I'm having the following problem:

       

      ./standalone.sh

      =========================================================================

       

        JBoss Bootstrap Environment

       

        JBOSS_HOME: /opt/jboss-as-7.1.1.Final

       

        JAVA: /usr/lib/jvm/java-openjdk/bin/java

       

        JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml

       

      =========================================================================

       

      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)

          ... 7 more

       

      The weird thing is that two days ago the server was working fine.

       

      I'm running Fedora 17.

       

      I've tried with fresh new copy of the server, a nightly build of jboss 7.2, same results.

       

      No serious updates.

       

      ¿any helpful hand?

       

      Thanks in advance and kind regards.

      Miguel