Details

    • Type: Bug Bug
    • Status: Closed Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 6.0.0.M2
    • Component/s: Logging
    • Security Level: Public (Everyone can see)
    • Labels:
      None
    • Environment:
      sun jdk6, fedora, AS trunk r96005
    • Similar Issues:
      Show 9 results 

      Description

      [jhalli jboss-6.0.0-SNAPSHOT]$ export JAVA_OPTS="-Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false"
      [jhalli jboss-6.0.0-SNAPSHOT]$ bin/run.sh
      =========================================================================

      JBoss Bootstrap Environment

      JBOSS_HOME: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/output/jboss-6.0.0-SNAPSHOT

      JAVA: /usr/local/jdk1.6.0_16/bin/java

      JAVA_OPTS: -Dprogram.name=run.sh -server -Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.net.preferIPv4Stack=true

      CLASSPATH: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/output/jboss-6.0.0-SNAPSHOT/bin/run.jar:/usr/local/jdk1.6.0_16/lib/tools.jar

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

      Failed to initalize plugin: org.jboss.logging.logmanager.LoggerPluginImpl@214a55f2, cause: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
      ...
      Failed to initalize plugin: org.jboss.aop.util.logging.SystemOutLoggerPlugin@5c1ae90c, cause: java.lang.AbstractMethodError

        Activity

        Hide
        Jonathan Halliday
        added a comment -

        $ export JAVA_OPTS="-Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl"
        $ bin/run.sh
        =========================================================================

        JBoss Bootstrap Environment

        JBOSS_HOME: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/target/jboss-6.0.0-SNAPSHOT

        JAVA: /usr/local/jdk1.6.0_17/bin/java

        JAVA_OPTS: -Dprogram.name=run.sh -server -Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl -Djava.net.preferIPv4Stack=true

        CLASSPATH: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/target/jboss-6.0.0-SNAPSHOT/bin/run.jar:/usr/local/jdk1.6.0_17/lib/tools.jar

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

        Could not load Logmanager "org.jboss.logmanager.LogManager"
        java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        at java.util.logging.LogManager$1.run(LogManager.java:166)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.util.logging.LogManager.<clinit>(LogManager.java:156)
        at java.util.logging.Logger.getLogger(Logger.java:273)
        at sun.management.snmp.util.MibLogger.<init>(MibLogger.java:57)
        at sun.management.snmp.util.MibLogger.<init>(MibLogger.java:42)
        at sun.management.jmxremote.ConnectorBootstrap.<clinit>(ConnectorBootstrap.java:760)
        at sun.management.Agent.startAgent(Agent.java:127)
        at sun.management.Agent.startAgent(Agent.java:239)
        Failed to initalize plugin: org.jboss.logging.logmanager.LoggerPluginImpl@58d9660d, cause: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")

        Show
        Jonathan Halliday
        added a comment - $ export JAVA_OPTS="-Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl" $ bin/run.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/target/jboss-6.0.0-SNAPSHOT JAVA: /usr/local/jdk1.6.0_17/bin/java JAVA_OPTS: -Dprogram.name=run.sh -server -Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl -Djava.net.preferIPv4Stack=true CLASSPATH: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/target/jboss-6.0.0-SNAPSHOT/bin/run.jar:/usr/local/jdk1.6.0_17/lib/tools.jar ========================================================================= Could not load Logmanager "org.jboss.logmanager.LogManager" java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:303) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at java.util.logging.LogManager$1.run(LogManager.java:166) at java.security.AccessController.doPrivileged(Native Method) at java.util.logging.LogManager.<clinit>(LogManager.java:156) at java.util.logging.Logger.getLogger(Logger.java:273) at sun.management.snmp.util.MibLogger.<init>(MibLogger.java:57) at sun.management.snmp.util.MibLogger.<init>(MibLogger.java:42) at sun.management.jmxremote.ConnectorBootstrap.<clinit>(ConnectorBootstrap.java:760) at sun.management.Agent.startAgent(Agent.java:127) at sun.management.Agent.startAgent(Agent.java:239) Failed to initalize plugin: org.jboss.logging.logmanager.LoggerPluginImpl@58d9660d, cause: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
        Hide
        David Lloyd
        added a comment -

        Sorry, forgot to mention that you also have to move jboss-logmanager.jar on to the boot classpath.

        Show
        David Lloyd
        added a comment - Sorry, forgot to mention that you also have to move jboss-logmanager.jar on to the boot classpath.
        Hide
        Jonathan Halliday
        added a comment -

        Then the steps to do so need documenting, or it needs to live there by default.

        Show
        Jonathan Halliday
        added a comment - Then the steps to do so need documenting, or it needs to live there by default.
        Hide
        David Lloyd
        added a comment -

        Aye, aye, cap'n. I'll update the Logger wiki page for now. We can explore moving the logmanager to the boot classpath at another time.

        Show
        David Lloyd
        added a comment - Aye, aye, cap'n. I'll update the Logger wiki page for now. We can explore moving the logmanager to the boot classpath at another time.
        Hide
        Paul Sideleau
        added a comment -

        I believe an additional step is required. I had a related issue enabling the aspectj load time weaver as a java agent. It required me to setup the same logging configuration changes that were included in this ticket. While testing on windows, I noticed it creating a "$

        {jboss.boot.server.log.dir}" directory for the boot.log file instead of placing it in the server's log directory. On one of our clustered linux servers, it was causing an error to triger:"${jboss.boot.server.log.dir}

        " is not a directory. I believe this is because all the systems properties have not been configured yet. I explicitly had to add -Djboss.boot.server.log.dir=/jboss-6.0.0.Final/server/default/log in addition to the parameters, -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl"

        This workaround will cause issues if you need to start up multiple jboss servers, such as "default" and "all".

        Is there a better approach for this?

        Show
        Paul Sideleau
        added a comment - I believe an additional step is required. I had a related issue enabling the aspectj load time weaver as a java agent. It required me to setup the same logging configuration changes that were included in this ticket. While testing on windows, I noticed it creating a "$ {jboss.boot.server.log.dir}" directory for the boot.log file instead of placing it in the server's log directory. On one of our clustered linux servers, it was causing an error to triger:"${jboss.boot.server.log.dir} " is not a directory. I believe this is because all the systems properties have not been configured yet. I explicitly had to add -Djboss.boot.server.log.dir=/jboss-6.0.0.Final/server/default/log in addition to the parameters, -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl" This workaround will cause issues if you need to start up multiple jboss servers, such as "default" and "all". Is there a better approach for this?

          People

          • Assignee:
            David Lloyd
            Reporter:
            Jonathan Halliday
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: