Bug 960979

Summary:	Upgrading to EAP 6.1 breaks tomcat6 from the EWS 1.0 channel
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Brenton Leanhardt <bleanhar>
Component:	distribution	Assignee:	jboss-set
Status:	CLOSED WONTFIX	QA Contact:	Len DiMaggio <ldimaggi>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-01 12:29:17 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:

Description Brenton Leanhardt 2013-05-08 12:44:54 UTC

Description of problem:
This is related to Bug #959993.  I'm not sure what component this should be filed against.  This bug likely only exists in the RPM distribution of EAP 6.1 and EWS 1.0.

Currently OpenShift Enterprise only support the jboss EWS 1.0 cartridge.  We previously instructed customers to use the EWS 1.0 RHN channel.  However we found that when upgrading the JBoss EAP cartridge to use the 6.1 content the EWS 1.0 cartridge would no longer be able to compile JSPs.

The workaround for OpenShift Enterprise is simply to have customers use the EWS 2.0 content sets for the EWS 1.0 cartridge as that does work as expected.  I'm filing this bug simply so that others can be aware in case they are affected.

If there are supported combinations of JBoss RHN channels it would be helpful for us to know.  Right now we are operating on the assumption that we will be able to have the EWS 2.0 content sets and the EAP 6 content sets enabled on the same machine.