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:
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:
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:
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:
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:
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:
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:
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.

Dani AI

Generated

Quick summary and a safe fix. ’s symptoms (log-manager class failing to load, then a VM error after you tried to change the boot classpath) point to two separate issues: the JBoss logging subsystem needs the JBoss log manager visible to the JVM bootstrap classloader, and accidentally replacing the JVM bootstrap path will remove core classes. Upgrading Java (good advice from for security) does not by itself change how JBoss modules and the bootstrap classloader interact.

Don’t use the plain -Xbootclasspath: form — that replaces the VM bootstrap path and can make core classes (java.lang.Object, etc.) disappear. Instead prepend the logmanager JAR with the /p form so you do not remove the default platform classes. The JVM docs explain the difference between -Xbootclasspath, -Xbootclasspath/p and -Xbootclasspath/a. (docs.oracle.com)

Preferred, supported approach for EAP/AS 6.x and WildFly is to set three JVM options (added to the server startup config rather than typed ad‑hoc at the prompt): add the JBoss modules system packages, set the java.util.logging.manager to the JBoss LogManager, and prepend the jboss-logmanager JAR to the boot classpath. On Windows put these into bin\standalone.conf.bat (or the domain equivalent) so quoting/linebreak issues don’t corrupt the value. Example (Windows) pattern: add a small loop to resolve the jboss-logmanager jar, then append the three options to JAVA_OPTS. AppDynamics/Splunk and other vendor docs use this exact pattern. (docs.appdynamics.com)

Checks and cautions: 1) If you see a VM NoClassDefFoundError for core classes it means the bootclasspath was overwritten — remove that change and try the /p prepend form. 2) Verify which Java the server actually uses; the java -version you run in a shell may differ from the binary the JBoss startup/service script picks up (the startup script honors JAVA_HOME/JRE_HOME and prints the JAVA it will use). 3) Make sure the logmanager class name and casing are exact and the jar path points at the JBoss modules copy. If the problem persists, capture the exact startup banner and the initial log-manager-related stack trace and post them (that output is what shows whether the bootstrap jar was found or if the module loader failed). ()

Recommended Answers

All 2 Replies

Any reason you have to be on obsolete Java 1.6?
The final security update to 1.6 (the one you have) was over a year ago, and you are now missing literally hundreds of fixes, including many "critical" fixes. For your own protection, and the protection of others sharing your network, you should update immediatly to current Java 1.8 version or (if necessary for some reason) the latest supported release of 1.7

I also tried updateing java to 1.7 and 1.8 but I was still getting same errors.

I have no idea what the problem could be. So I am use any suggestion.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.