Bug 1185453 – Tomcat server.xml is empty causing SAXParseException upon startup

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1185453 - Tomcat server.xml is empty causing SAXParseException upon startup

Summary:	Tomcat server.xml is empty causing SAXParseException upon startup

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Image (Show other bugs)
Sub Component:
Version:	2.2.0
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Jason DeTiberus
QA Contact:	libra bugs
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1175489
Blocks:
	Show dependency tree / graph

Reported:	2015-01-23 14:34 EST by Brenton Leanhardt
Modified:	2015-02-12 08:10 EST (History)
CC List:	11 users (show)

See Also:
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 08:10:00 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2015:0220	normal	SHIPPED_LIVE	Red Hat OpenShift Enterprise 2.2.4 bug fix and enhancement update	2015-02-12 13:08:20 EST

Groups: None (edit)

Comment 3 Gaoyun Pei 2015-01-26 01:16:19 EST

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 08:10:00 EST

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

Note You need to log in before you can comment on or make changes to this bug.