Bug 1222855

Summary: [GSS](6.4.z) When EAP is run as a service in linux, the working directory is "/"
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Oscar Molina <omolinab>
Component: Scripts and CommandsAssignee: baranowb <bbaranow>
Status: CLOSED CURRENTRELEASE QA Contact: Peter Mackay <pmackay>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: bbaranow, bmaxwell, cdewolf, dpospisi, fnasser, jbilek, omolinab, pcheung, pgier, pkremens, pmackay, rsvoboda, tcerar
Target Milestone: CR1   
Target Release: EAP 6.4.7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 11:55:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1279552    

Description Oscar Molina 2015-05-19 10:09:44 UTC
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:

Comment 2 Oscar Molina 2015-05-19 13:01:41 UTC
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.

Comment 9 Peter Mackay 2016-03-04 07:40:05 UTC
Verified with EAP 6.4.7.CP.CR2

Comment 10 Petr Penicka 2017-01-17 11:55:36 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.