Description of problem: When you run EAP as a service in a linux environment, it starts in the directory "/" by default regardless of the user. The application starts without problems because all directories or files that have to be created on runtime have the correct path, but sometimes some of them are created in the working path and then an error appears. Could the jboss service init scripts be modified to set the working directory to $JBOSS_HOME for instance when the service is started? How reproducible: Install JBoss EAP 6.4 as a service and check the working directory. Steps to Reproduce: 1. Install JBoss EAP 6.4 as a service. 2. Modify <JBOSS_HOME>/bin/standalone.sh script adding the command "pwd" for viewing the default path. 3. Start JBoss EAP service. 4. Look at the server.log file. Actual results: The working directory is "/". Expected results: The working directory could be $JBOSS_HOME or it can be parametrized so customer can modify it. Additional info:
Hi Bartosz, Sorry for that information. I've tested on version 6.4.0 and I've configured JBoss EAP 6 as a Service in Red Hat Enterprise Linux (Zip, Installer). Don't hesitate to contact with me if you need more information. Best regards, Oscar.
Verified with EAP 6.4.7.CP.CR2
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.