Wildfly on path with spaces

[ladniros]

I can find very little information online about this newer than 10 years old, leading me to believe I must be missing something very obvious or doing something wrong.

We have an izpack installer that installs Wildfly to somewhere on the client's server. Typically this is the root of the C drive in Windows. No one tried installing it elsewhere until recently. Aside from some bugs that needed fixing in our installer, I discovered that Wildfly simply won't start if it is installed along a path that has spaces in it. I need to find out if this is something we will need to restrict and deal with, or if there's some file I can update somewhere to fix this (This is Wildfly 10.1.0).

All I get in the stdout log file is:

2019-12-20 07:53:58 Commons Daemon procrun stdout initialized

Calling "C:\path with spaces\wildfly-10.1.0.Final\bin\standalone.conf.bat"

Setting JAVA property to "C:\Program Files\Java\jdk1.8.0_221\bin\java"

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

JBoss Bootstrap Environment

JBOSS_HOME: "C:\path with spaces\wildfly-10.1.0.Final"

JAVA: "C:\Program Files\Java\jdk1.8.0_221\bin\java"

JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms6144M -Xmx6144M -XX:MaxMetaspaceSize=512M -Djboss.as.management.blocking.timeout=600 -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.security.properties=file:C:\path with spaces\wildfly-10.1.0.Final\cfms4-java.security"

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

And this appears in the stderr log:

2019-12-20 07:53:58 Commons Daemon procrun stderr initialized

Error: Could not find or load main class with

(that's exactly how it ends, there's nothing after "with").

And there is no server.log.

[ctomc]

WildFly will start just fine on paths with spaces with it. As long as you properly set it up.

Given that you are using windows service as means to run it, what script / configuration are you using for it?

the one that comes with WildFly in docs/contrib? or your own script to setup procrun deamon?

I would recommend that you use WildFly provided scripts to for configuring service as they ware reasonably tested for such scenarios.

you can find them in docs/contrib directory of wildfly distribution, or you can always grab latest at wildfly-core/core-feature-pack/src/main/resources/content/docs/contrib/scripts/service at master · wildfly/wildfly-core …

to make it work read the comments in the service.bat file itself. wildfly-core/service.bat at master · wildfly/wildfly-core · GitHub

[someguy1234567890]

Yes, we are using the service installer that comes with Wildfly. The only thing that happens when trying to start is the above content in the log files mentioned. Removing the spaces makes it start. What script would I go about fixing this in, and how so?