Bug 1058410

Summary:	Defer support for space char in install path for FSW6 - issues with Security Manager configuration
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Len DiMaggio <ldimaggi>
Component:	Configuration	Assignee:	Julian Coleman <jcoleman>
Status:	CLOSED CANTFIX	QA Contact:	Jiri Sedlacek <jsedlace>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	atangrin, dcoleman, dlesage, kconner, oskutka, soa-p-jira
Target Milestone:	---
Target Release:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	The jboss-cli tool will not launch successfully on the Microsoft Windows operating system if JBoss EAP is installed in a directory that has spaces or other special characters such as parentheses in its path. The following error message is the outcome if JBoss EAP is 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 can be worked around by editing the jboss-cli.bat file and editing line 62 of jboss-cli.bat to move the first “ character from the beginning of JAVA_OPTS to after the assignment so it looks like the following. ---- set JAVA_OPTS="%JAVA_OPTS% -Djboss.modules.system.pkgs=com.sun.java.swing -Dlogging.configuration=file:%JBOSS_HOME%\bin\jboss-cli-logging.properties" ---- This error can also be avoided by not installing JBoss EAP 6 in a directory with spaces or parentheses in its name. This will be fixed in a future release.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-30 09:18:34 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:	1031173
Bug Blocks:

Description Len DiMaggio 2014-01-27 18:05:29 UTC

Description of problem:

See:  https://bugzilla.redhat.com/show_bug.cgi?id=1031173



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 kconner 2014-01-28 12:34:21 UTC

I have a workaround for the security manager configuration however the above report actually refers to a problem with the EAP jboss-cli script and not the security manager.