Bug 1185453

Summary:	Tomcat server.xml is empty causing SAXParseException upon startup
Product:	OpenShift Container Platform	Reporter:	Brenton Leanhardt <bleanhar>
Component:	ImageStreams	Assignee:	Jason DeTiberus <jdetiber>
Status:	CLOSED ERRATA	QA Contact:	libra bugs <libra-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.2.0	CC:	bparees, chunchen, cparham, cryan, gpei, jhadvig, jokerman, libra-bugs, libra-onpremise-devel, mmccomas, wsun
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openshift-origin-cartridge-jbosseap-2.24.0.1-1, openshift-origin-cartridge-jbossews-1.32.0.1-1	Doc Type:	Bug Fix
Doc Text:	Cause: A bug in environment variable parsing led to JBOSS EAP and EWS server.xml being removed when environment variables contained whitespace. Consequence: Tomcat would fail to start up. Fix: Environment variable handling has been updated to handle whitespace properly. Result: Environment variables with whitespace no longer break JBOSS EAP and EWS applications.	Story Points:	---
Clone Of:	1175489	Environment:
Last Closed:	2015-02-12 13:10:00 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:	1175489
Bug Blocks:

Comment 3 Gaoyun Pei 2015-01-26 06:16:19 UTC

Verify this bug on puddle 2.2/2015-01-23.2

1. Create a jbosseap app with jenkins client
rhc app create eap jbossews-1 --enable-jenkins

2. Set an env variables with its value contain *blank* character
[root@broker ~]# rhc env-set OPENSHIFT_TEST=va' 'l"u"e1 -a eap
Setting environment variable(s) ... done
[root@broker ~]# rhc env-list -a eap
OPENSHIFT_TEST=va lue1

3. Open Jenkins job and click Build Now

4. Watch console output. No error was found, jbosseap cartridge could start.

5. This also works well against jbossews-1/jbossew-2 cartridge

Comment 5 errata-xmlrpc 2015-02-12 13:10:00 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0220.html