Jboss log manager error

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • game2d
    New Member
    • Apr 2013
    • 59
    #1

    Jboss log manager error

    I am trying to start up JBoss with parameters in Windows but getting some errors. If I remove parameters than JBoss startup iwht no errors. Could some one please take a look.



    environment variables:

    Code:
    JAVA_HOME=C:\Java\jdk1.6.0_45
JBOSS_HOME=C:\bin\jboss-eap-6.1
Path=C:\Java\jdk1.6.0_45\bin;C:\WINDOWS\system32;
    start up jboss with following parameters:

    Code:
    set "JAVA_OPTS=%JAVA_OPTS% 
    -Djava.rmi.server.hostname=myhost
    -Dcom.sun.management.jmxremote.port=myport
    -Dcom.sun.management.jmxremote.ssl=false
    -Dcom.sun.management.jmxremote.authenticate=true
   -Dcom.sun.management.jmxremote.password.file=C:\Java\jdk\jre\lib\management\jmx.password
   -Dcom.sun.management.jmxremote.access.file=C:\Java\jdk\jre\lib\management\jmx.access
"
    Error:

    Code:
    WARNING: failed to load the specified log manager class org.jboss.logmanager.LogManager
Error: Operation <"parallel-extension-add"> failed - address:<[]>
                   java.lang.RuntimeException: failed initializing module org.jboss.as.logging
    =============== =============== =============== =============== ==============

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

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

    so to fix the error above. I have added logmanager parameter below.

    start up jboss using parameters:


    Code:
    set "JAVA_OPTS=%JAVA_OPTS%
-Djava.util.logging.manager=org.jboss.logmanager.LogManager
-Djava.rmi.server.hostname=myhost
-Dcom.sun.management.jmxremote.port=myport
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=C:\Java\jdk\jre\lib\management\jmx.password
-Dcom.sun.management.jmxremote.access.file=C:\Java\jdk\jre\lib\management\jmx.access
​"


    ERROR:

    Code:
    Could not load Logmanager "org.jboss.logmanager.LogManager"
java.lang.ClassNotFoundException: org.jboss.logmanager.logManager


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

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

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



    so to fix error above. I have added -xbootclasspath parameter.

    start up jboss using parameters:


    Code:
    set "JAVA_OPTS=%JAVA_OPTS%
-Djava.util.logging.manager=org.jboss.logmanager.LogManager"
-Xbootclasspath:C:\bin\jboss-eap-6.1\modules\system\layers\base\org\jboss\logmanager\main\jboss-logmanager-1.4.0.Final-redhat-1.jar

-Djava.rmi.server.hostname=myhost
-Dcom.sun.management.jmxremote.port=myport
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=C:\Java\jdk\jre\lib\management\jmx.password
-Dcom.sun.management.jmxremote.access.file=C:\Java\jdk\jre\lib\management\jmx.access
​"


    ERROR:

    Code:
    Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object


    and now I have no idea what to do. I have tried reinstalling jdk but no luck.

    when I enter "java -version" in CMD. Than I get result: "1.6.0_45". So I know jdk is set up. but when I start Jboss than jdk is not initialization.
    Tags: None
    • chaarmann
      Recognized Expert Contributor
      • Nov 2007
      • 785
      #2
      Can you type "where java" in CMD?
      It should point to directory "C:\Java\jdk1.6 .0_45" (because I noticed that you use directory "C:\Java\jdk\jr e\" for jmxremote).

      Can you also please print out the value of your JAVA_OPTS by typing "echo %JAVA_OPTS%"? Just verify that if there is a -classpath (or -cp) option that it points to "C:\Java\jdk1.6 .0_45"

      Otherwise, assuming that you haven given all the directories to the libraries correctly, then maybe the class is missing inside the library?
      You can open the jar-file in "C:\bin\jbo ss-eap-6.1" with a zip program and look if the file LogManager.jar is inside directory org/jboss/logmanager.
      If not, your jar-file is corrupt and you need to download a new one.

      By the way, my memories about jboss faded, but it is strange that it is installed in "C:\bin\jbo ss-eap-6.1" (as given by you in JBOSS_HOME) and not in "C:\jboss-eap-6.1\bin". Are you sure that this path is correct?

      Also please remove the XBootclasspath, it is normally used for overriding original classes during startup and I bet it will not solve problems, but create new ones.

        Comment

        • game2d
          New Member
          • Apr 2013
          • 59
          #3
          ***note*** When If I dont add parameters in JAVA_OPTS Than jboss starts up corretly.
          ***note*** i dont have 'CLASSPATH' Environment Variable set up.
          ***note*** I have update java to 1.7, and I have paste full stacktrace with all info. still same issue.


          in CMD:
          Code:
          where java = C:\Java\jdk1.7.0_60_X64\bin\java.exe
JAVA_HOME = C:\Java\jdk1.7.0_60_X64
JBOSS_HOME: C:\jboss-eap-6.1
Path=C:\Java\jdk1.7.0_60_X64\bin;C:\Windows\system32;
          -----

          I found 3 "logmanager.jar " files. not sure if u mean these.

          Code:
          C:\jboss-eap-6.1\modules\system\layers\base\org\jboss\logmanager\main\jboss-logmanager-1.4.0.Final-redhat-1.jar
C:\jboss-eap-6.1\modules\system\layers\base\org\jboss\log4j\logmanager\main\log4j-jboss-logmanager-1.0.1.Final-redhat-2.jar
C:\jboss-eap-6.1\modules\system\layers\base\org\jboss\logging\main\jboss-logging-3.1.2.GA-redhat-1.jar
          ----



          start jboss with parameters and stacktrace.

          Code:
          C:\jboss-eap-6.1\bin>standalone.bat
Calling "C:\jboss-eap-6.1\bin\standalone.conf.bat"
===============================================================================
  JBoss Bootstrap Environment


  JBOSS_HOME: C:\jboss-eap-6.1
  JAVA_HOME: C:\Java\jdk1.7.0_60_X64
  JAVA: C:\Java\jdk1.7.0_60_X64\bin\java

 
  JAVA_OPTS: -XX:+TieredCompilation -XX:+UseCompressedOops -Dprogram.name=standa
lone.bat -Xms1303M -Xmx1303M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=tru
e -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.util.logging.manager=org.
jboss.logmanager.LogManager -Djava.rmi.server.hostname=myhost -Dcom.sun.manag
ement.jmxremote=true -Dcom.sun.management.jmxremote.port=myport -Dcom.sun.manageme
nt.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=true -Dcom.su
n.management.jmxremote.password.file=C:\Java\jdk1.7.0_60_X64\jre\lib\management\
jmxremote.password -Dcom.sun.management.jmxremote.access.file=C:\Java\jdk1.7.0_6
0_X64\jre\lib\management\jmxremote.access

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

 

Could not load Logmanager "org.jboss.logmanager.LogManager"
java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
        at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
        at java.util.logging.LogManager$1.run(LogManager.java:191)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.util.logging.LogManager.<clinit>(LogManager.java:181)
        at java.util.logging.Logger.demandLogger(Logger.java:339)
        at java.util.logging.Logger.getLogger(Logger.java:393)
        at com.sun.jmx.remote.util.ClassLogger.<init>(ClassLogger.java:55)
        at sun.management.jmxremote.ConnectorBootstrap.<clinit>(ConnectorBootstr
ap.java:823)

        at sun.management.Agent.startAgent(Agent.java:260)
        at sun.management.Agent.startAgent(Agent.java:456)

WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
Jun 26, 2014 11:40:41 AM org.jboss.msc.service.ServiceContainerImpl <clinit>
INFO: JBoss MSC version 1.0.4.GA-redhat-1
Jun 26, 2014 11:40:42 AM org.jboss.as.server.ApplicationServerService start
INFO: JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
Jun 26, 2014 11:40:44 AM org.jboss.as.controller.AbstractOperationContext executeStep

 

ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([])
java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging
        at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:99)
        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440)
        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322)
        at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229)
        at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224)
        at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:232)
        at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:225)
        at org.jboss.as.server.ServerService.boot(ServerService.java:333)
        at org.jboss.as.server.ServerService.boot(ServerService.java:308)
        at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:188)
        at java.lang.Thread.run(Thread.java:745)

[B][I]Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException:
JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager.
The subsystem has not be initialized and cannot be used.
To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"[/I][/B]
        at java.util.concurrent.FutureTask.report(FutureTask.java:122)
        at java.util.concurrent.FutureTask.get(FutureTask.java:188)
        at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:91)
        ... 10 more

Caused by: java.lang.IllegalStateException: JBAS011592:
The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager.
The subsystem has not be initialized and cannot be used.
To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
        at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:103)
        at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97)
        at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127)
        at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:113)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
        at org.jboss.threads.JBossThread.run(JBossThread.java:122)

 

Jun 26, 2014 11:40:44 AM org.jboss.as.server.ServerService boot
FATAL: JBAS015957: Server boot has failed in an unrecoverable manner; exiting. S
ee previous messages for details.
Press any key to continue . . .


          Solution?

          by looking at the stacktrace it says:

          The subsystem has not be initialized and cannot be used(in bold).

          To use JBoss Log Manager you must add the system property "java.util.logg ing.manager" and set it to "org.jboss.logm anager.LogManag er"



          so I guess this is the problem? if yes than how to initialized to subsystem?

            Comment

            • DavidHT
              New Member
              • Nov 2014
              • 1
              #4
              You have a quotes of more in:

              -Djava.util.logg ing.manager=org .jboss.logmanag er.LogManager"

              Isn't it?

                Comment

                Previous template Next
                Working...