Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 6.0.0.M2
    • Component/s: Logging
    • Labels:
      None
    • Environment:

      sun jdk6, fedora, AS trunk r96005

      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

        Gliffy Diagrams

          Activity

          Hide
          dmlloyd David Lloyd added a comment -

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

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

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

          Show
          jhalliday Jonathan Halliday added a comment - Then the steps to do so need documenting, or it needs to live there by default.
          Hide
          dmlloyd 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
          dmlloyd 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
          p2auljr 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
          p2auljr 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?
          Hide
          ozslater Oz Slater added a comment -

          Same issue as Paul Sideleau on JBoss 6.1.0.Final,

          {jboss.boot.server.log.dir} is not resolving and JBoss literally creating a "${jboss.boot.server.log.dir}

          " directory to save boot.log. No problem with

          {jboss.server.log.dir}

          though.

          Show
          ozslater Oz Slater added a comment - Same issue as Paul Sideleau on JBoss 6.1.0.Final, {jboss.boot.server.log.dir} is not resolving and JBoss literally creating a "${jboss.boot.server.log.dir} " directory to save boot.log. No problem with {jboss.server.log.dir} though.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development