Bug 959841

Summary:	Update Tomcat 6 and 7 for EWS 2.0.1
Product:	[JBoss] JBoss Enterprise Web Server 2	Reporter:	Weinan Li <weli>
Component:	tomcat6, tomcat7	Assignee:	Mladen Turk <mturk>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Libor Fuka <lfuka>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.0.1	CC:	jclere, jdoyle, majoshi, mhasko, mhusnain, mturk, myarboro, pslavice
Target Milestone:	---
Target Release:	2.0.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	JBoss Enterprise Web Server's included Tomcat 6 and 7 packages were out of date. The most recent versions of Tomcat 6 (6.0.37) and Tomcat 7 (7.0.40) are now included in JBoss Enterprise 2.0.1. As a result, both versions of Tomcat now work as expected.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-03 12:58:56 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:
Bug Blocks:	956987, 956990, 962270, 962719, 962720, 963094

Description Weinan Li 2013-05-06 05:50:31 UTC

* Tomcat 6 needs to be updated to 6.0.37
* Tomcat 7 needs to be updated to 7.0.39

Please note we have new branches to build the updated Tomcats:

* jb-eap-6.0.1-rhel-6 
* dist-5E-ep-6.0.1

So we won't mix up the older version of Tomcats in EWS 2.0.0

Comment 1 Jean-frederic Clere 2013-05-08 15:11:04 UTC

* Tomcat 7 needs to be updated to 7.0.40 :D

Comment 2 Mandar Joshi 2013-05-29 18:11:20 UTC

Added DocText.

@Jean-frederic Clere, can you please review the Doc Text content?

Comment 3 Misha H. Ali 2013-05-30 01:08:00 UTC

This bug's status is still set to NEW. Is this is a resolved issue, as the CCFR information suggests, or is this still unresolved?

Comment 4 Weinan Li 2013-05-30 03:00:10 UTC

This is not yet finished and planned to be put into CR1 next week.

Comment 5 Libor Fuka 2013-06-06 08:32:43 UTC

There are still directories with names apache-tomcat-6.0.35 and apache-tomcat-7.0.30 in Windows/Solaris zips.
Its not good way to have directories names with tomcat version numbers. There is simple directory name tomcat6 and tomcat7 in RHEL zips.
If we stay with tomcat version directories names in Sol/Win zips we will need the update directory name after each tomcats upgrade.

Comment 6 Weinan Li 2013-06-06 08:45:23 UTC

Hi Mladen, Could you please help to handle this? Thanks!

Comment 7 Libor Fuka 2013-06-06 08:53:20 UTC

If i remember we upgraded tomcats to 7.0.40 and 6.0.37, don't i ?

Comment 8 Mladen Turk 2013-06-06 08:54:24 UTC

First directories are now apache-tomcat-6.0.37 and apache-tomcat-7.0.40
As part of postinstall scripts for windows symlink is created named
tomcat6 that points to current apache-tomcat-6.0.xx and
tomcat7 that points to current apache-tomcat-7.0.xx

Think this is something both very versatile and users are so far accustomed
to it since it's been like from EWS1 onwards. I'd suggest to don't change that.

Also we won't need to have directory name update because we won't be
(or at least should not) change tomcat version within a release.

Comment 9 Libor Fuka 2013-06-06 09:05:41 UTC

sorry, directory names are ok with new versions
It was my fault.

Comment 10 Michal Haško 2013-06-06 14:22:01 UTC

VERIFIED on 2.0.1-CR1 on RHEL5,6 tomcat6,7.

Comment 11 Misha H. Ali 2013-06-07 04:06:48 UTC

Added release note. If this incorrect, please correct.

Comment 12 Weinan Li 2013-06-07 06:00:55 UTC

Maybe it's better to tell users that multiple CVEs and known issues have been fixed in these releases.

Comment 14 Libor Fuka 2013-06-07 06:59:54 UTC

Tomcats upgrade to 6.0.37 and 7.0.40

Verified on EWS 2.0.1 CR1 on MS Windows 2008 32/64bit, MS Windows 2008R2 - OracleJDK1.6, OracleJDK1.7

Comment 15 Libor Fuka 2013-06-07 07:10:58 UTC

Verified on EWS 2.0.1 CR1 on Solaris 10,11 Intel 32/64bit, Solaris SPARC 10, 11 - OracleJDK 1.6, 1.7