Bug 1037601

Summary: Windows 2008 - Unable to install the agent when JAVA_HOME contains parenthesis
Product: [JBoss] JBoss Operations Network Reporter: Filip Brychta <fbrychta>
Component: InstallerAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Filip Brychta <fbrychta>
Severity: medium Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: ahovsepy, jshaughn
Target Milestone: ER01   
Target Release: JON 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-11 13:59:57 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:
Attachments:
Description Flags
installer.log none

Description Filip Brychta 2013-12-03 13:02:40 UTC 
Created attachment 832040 [details]
installer.log

Description of problem:
By default 32b jdk is installed to 'C:\Program Files (x86)\Java' on 64b Windows 2008. Installation of rhq agent (using rhqctl) then fails.

Version-Release number of selected component (if applicable):
Version :	
3.2.0.ER7
Build Number :	
e8e6401:ff0061d

How reproducible:
Always

Steps to Reproduce:
1. java is installed to 'C:\Program Files (x86)\Java'
2. JAVA_HOME is set to C:\Program Files (x86)\Java\Java\jdk1.7.0_45
3. unzip jon-server-3.2.0.ER7.zip
4. rhqctl install

Actual results (see attached installer.log for bigger context):
Storage and server are installed successfully but the agent installation fails:
23:09:47,604 INFO  [org.rhq.server.control.command.Install] Updating RHQ Agent S
ervice...
\Java\jdk1.7.0_45\bin\java.exe" "-Djava.endorsed.dirs was unexpected at this tim
e.

Expected results:
Installation is successful

Additional info:
Workaround: install the java to some directory without parenthesis in the path
Originally found as a part of bz 1022620
It could be difficult to find a root cause of this issue.
Comment 2 Jay Shaughnessy 2014-08-27 20:54:14 UTC 
This is already fixed in the 3.3.0 branch.
Comment 3 Filip Brychta 2014-08-28 13:32:51 UTC 
Verified on
Version :	
3.3.0.ER01.1
Build Number :	
9941660:f3aa7e7