4 Replies Latest reply on Dec 22, 2015 10:38 PM by Ben Han

    How to start up jboss in windows with parameters?

    gamer2d Newbie

      Hello,

      I am new to jboss and I just downloaded jboss folder on my windows.I am having super hard time starting up jboss. I was able to startup jboss without any parameters  and it works fine.

       

      Problem:

      The problem is when ever I add port in my parameters than I get an error. I am not sure if I need to change some xml file or something.... I have no idea how to fix this. Any help will be greatly appreciated!!!

       

      I want to start up jboss with following parameters.

       

      -Djava.util.logging.manager=org.jboss.logmanager.LogManager

      -Djava.rmi.server.hostname=127.0.0.1

      -Dcom.sun.management.jmxremote=true

      -Dcom.sun.management.jmxremote.port=8080

      -Dcom.sun.management.jmxremote.ssl=false

      -Dcom.sun.management.jmxremote.authenticate=true

      -Dcom.sun.management.jmxremote.password.file=C:\Java\jdk1.7\jre\lib\management\jmxremote.password

      -Dcom.sun.management.jmxremote.access.file=C:\Java\jdk1.7\jre\lib\management\jmxremote.access

       

       

       

       

       

       

      This is the error I get.

       

       

       

      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

        JAVA: C:\Java\jdk1.7\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=127.0.0.1 -Dcom.sun.manag

      ement.jmxremote=true -Dcom.sun.management.jmxremote.port=8080 -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>(ConnectorBootstrap.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

      Jul 23, 2014 2:18:50 PM org.jboss.msc.service.ServiceContainerImpl <clinit> INFO: JBoss MSC version 1.0.4.GA-redhat-1

      Jul 23, 2014 2:18:50 PM org.jboss.as.server.ApplicationServerService start INFO: JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting

      Jul 23, 2014 2:18:51 PM 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)

       

       

      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"

              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)

       

       

      Jul 23, 2014 2:18:51 PM org.jboss.as.server.ServerService boot

      FATAL: JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

      Press any key to continue . . .

        • 1. Re: How to start up jboss in windows with parameters?
          Ricki Lambert Newbie

          bumping this as i am getting a similar error message (which by the way only occurs when you provide the jmx parameters - remove those and I bet it will start)

           

          if [ "x$JAVA_OPTS" = "x" ]; then

             JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true"

             JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"

             JAVA_OPTS="$JAVA_OPTS -Duser.timezone=GMT"

             JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager"

             JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote"

             JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=9999"

             JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.ssl=false"

             JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.authenticate=false"

             JAVA_OPTS="$JAVA_OPTS -Djava.rmi.server.hostname=94.5.19.27"

            # JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"

           

           

           

          Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

          Could not load Logmanager "org.jboss.logmanager.LogManager"

          java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager

                  at java.net.URLClassLoader$1.run(URLClassLoader.java:372)

                  at java.net.URLClassLoader$1.run(URLClassLoader.java:361)

                  at java.security.AccessController.doPrivileged(Native Method)

                  at java.net.URLClassLoader.findClass(URLClassLoader.java:360)

                  at java.lang.ClassLoader.loadClass(ClassLoader.java:424)

                  at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)

                  at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

                  at java.util.logging.LogManager$1.run(LogManager.java:195)

                  at java.util.logging.LogManager$1.run(LogManager.java:181)

                  at java.security.AccessController.doPrivileged(Native Method)

                  at java.util.logging.LogManager.<clinit>(LogManager.java:181)

                  at java.util.logging.Logger.demandLogger(Logger.java:448)

                  at java.util.logging.Logger.getLogger(Logger.java:502)

                  at com.sun.jmx.remote.util.ClassLogger.<init>(ClassLogger.java:55)

                  at sun.management.jmxremote.ConnectorBootstrap.<clinit>(ConnectorBootstrap.java:814)

                  at sun.management.Agent.startAgent(Agent.java:257)

                  at sun.management.Agent.startAgent(Agent.java:447)

          WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager

          Aug 04, 2014 5:34:25 PM org.jboss.msc.service.ServiceContainerImpl <clinit>

          INFO: JBoss MSC version 1.0.4.GA-redhat-1

          Aug 04, 2014 5:34:25 PM org.jboss.as.server.ApplicationServerService start

          INFO: JBAS015899: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) starting

          Aug 04, 2014 5:34:26 PM 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:607)

                  at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:485)

                  at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:282)

                  at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:277)

                  at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:269)

                  at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:291)

                  at org.jboss.as.server.ServerService.boot(ServerService.java:349)

                  at org.jboss.as.server.ServerService.boot(ServerService.java:324)

                  at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:253)

                  at java.lang.Thread.run(Thread.java:745)

          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"

                  at java.util.concurrent.FutureTask.report(FutureTask.java:122)

                  at java.util.concurrent.FutureTask.get(FutureTask.java:192)

                  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:110)

                  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:266)

                  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

                  at java.lang.Thread.run(Thread.java:745)

                  at org.jboss.threads.JBossThread.run(JBossThread.java:122)

          • 2. Re: How to start up jboss in windows with parameters?
            Max Rydahl Andersen Master

            is this from the command line or from when launching in eclipse ?

             

            btw. first thing I recommend when seeing issues like this especially on windows - make sure you quote your arguments so any special characters doesnt confuse the shell

            • 3. Re: How to start up jboss in windows with parameters?
              Paolo Menon Newbie

              First thing you need to make sure that jmxremote port you are setting is not in use. I will suggest to not use the same jboss default port.

              Second thing is that exception, to fix that you will need to add this lines here:


              windows:

               

              set "JAVA_OPTS=%JAVA_OPTS% -Xbootclasspath/p:../modules/org/jboss/logmanager/main/jboss-logmanager-1.2.2.GA.jar"

              set "JAVA_OPTS=%JAVA_OPTS% -Xbootclasspath/p:../modules/org/jboss/logmanager/log4j/main/jboss-logmanager-log4j-1.0.0.GA.jar"

              set "JAVA_OPTS=%JAVA_OPTS% -Xbootclasspath/p:../modules/org/apache/log4j/main/log4j-1.2.16.jar"

              set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.system.pkgs=org.jboss.logmanager"

               

              linux:


              JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:../modules/org/jboss/logmanager/main/jboss-logmanager-1.2.2.GA.jar"

              JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:../modules/org/jboss/logmanager/log4j/main/jboss-logmanager-log4j-1.0.0.GA.jar"

              JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:../modules/org/apache/log4j/main/log4j-1.2.16.jar"

              JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=org.jboss.logmanager"

               

              You  may need to change the jar file's version, just make sure they are in your jboss modules.

               

              Hope that's help

              • 4. Re: How to start up jboss in windows with parameters?
                Ben Han Newbie

                The same error occurs when I try to start an embedded WildFly AS server by run maven test.

                From the stack trace, we can see we need to add "java.util.logging.manager=org.jboss.logmanager.LogManager" as a system property, but how and where? I have tried many kinds of way but all failed.

                Finally, I found it's the pom.xml file works as following:

                  ...

                  <build>

                    <pluginManagement>

                      <plugins>

                        <plugin>

                          <artifactId>maven-surefire-plugin</artifactId>

                          <configuration>

                            <systemPropertyVariables>

                            <java.util.logging.manager>org.jboss.logmanager.LogManager</java.util.logging.manager>

                            </systemPropertyVariables>

                         </configuration>

                ...

                 

                Hope this can help you also.