The `jboss-cli` tool would not launch successfully on Microsoft Windows if JBoss EAP 6 was installed in a directory that had spaces or other special characters such as parentheses in its path. For example, the following error message was displayed if JBoss EAP 6 was installed in the directory `C:\JBoss EAP\jboss-eap-6.2`:
Error: Could not find or load main class EAP\jboss-eap-6.2\bin\jboss-cli-logging.properties
This issue has been fixed in this release by changing how the `jboss-cli` tool declares and uses file paths on Microsoft Windows. As a result, it can be used without workarounds in JBoss EAP 6 installations in directories that have spaces or other special characters in their path on Microsoft Windows systems.
Description of problem:
Canot run jboss-cli.bat on Windows when EAP unziped into directory with spaces
Version-Release number of selected component (if applicable):
Tested with jboss-as-dist-7.3.0.Final-redhat-10.zip
and then check with jboss-as-dist-7.3.0.Final-redhat-12.zip
Zips can be downloaded from
Steps to Reproduce:
1.On Windows 7 unzip EAP into directory with spaces.
Ex. C:\Users\John\Bug Example
2.Run C:\Users\John\Bug Example\jboss-eap-6.2\bin\jboss-cli.bat
Error: Could not find or load main class Example\jboss-eap-6.2\bin\jboss-cli-log
Press any key to continue . . .
You are disconnected at the moment. Type 'connect' to connect to the server or '
help' for the list of supported commands.
set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.system.pkgs=com.sun.java.swing"
set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.system.pkgs=com.sun.java.swing -Dlogging.configuration=file:%JBOSS_HOME%\bin\jboss-cli-logging.properties"
*** Bug 1033200 has been marked as a duplicate of this bug. ***
Please include there is a simple workaround for the issue, see
Also special characters like parentheses are problem here, we should add this to RN as well.
Verified on EAP 6.3.0.DR0