Bug 899449 (JBEWS-137)

Summary: Upgrade mod_jk to 1.2.3x
Product: [JBoss] JBoss Enterprise Web Server 2 Reporter: Samuel Mendenhall <smendenh>
Component: mod_jkAssignee: Weinan Li <weli>
Status: CLOSED CURRENTRELEASE QA Contact: Libor Fuka <lfuka>
Severity: high Docs Contact:
Priority: high    
Version: 2.0.0CC: jawilson, jclere, jdoyle, majoshi, mhasko, mhusnain, mturk, pcheung, pslavice, rhatlapa, rsvoboda, weli
Target Milestone: ---   
Target Release: 2.0.1   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEWS-137
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Attempts to manage multiple nodes using the status manager URL fails due to an issue with mod_jk version shipped with JBoss Enterprise Web Server 2.0. JBoss Enterprise Web Server 2.0.1 contains the updated mod_jk version 1.2.37. As a result, the status manager URL manages multiple nodes as expected.
 Story Points: ---
Clone Of:
: 899450 956513 956801 (view as bug list) Environment:
Last Closed: 2014-01-03 12:58:31 UTC Type: Task
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: 956513, 956801    

Description Samuel Mendenhall 2011-06-22 15:21:06 UTC 
Affects: Release Notes
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000006kvbY&sfdc.override=1
project_key: JBEWS

Once https://issues.apache.org/bugzilla/show_bug.cgi?id=51417 is fixed upstream and included in the next mod_jk, I assume 1.2.32, we need to upgrade to this version and include it in the EWS/EAP
Comment 1 Russell Dickenson 2011-08-26 03:37:32 UTC 
Triaged for RNs. Pending resolution.
Comment 2 Russell Dickenson 2011-08-26 03:37:32 UTC 
Release Notes Docs Status: Added: Not Yet Documented
Comment 3 Russell Dickenson 2011-08-29 05:57:34 UTC 
Writer: Added: ekopalov
Comment 4 Russell Dickenson 2011-08-30 04:54:21 UTC 
With the release of EAP 5.1.2 pending, all relevant JIRA issues which are open are being reviewed. Please confirm the current status of this issue and if it's incorrect, change it as required. Of particular interest are those which have been resolved: whether the cause is known but not yet fixed or the cause is known AND has been fixed.

For issues which are resolved, please provide appropriate Release Notes text, following the format of providing the Cause, Consequence, Fix and Result. From this information we will write the final release notes for all issues. A best effort is all that we ask of you.

Your review will help us that EAP 5.1.2's release notes are as accurate and complete as possible.

Thankyou.

Engineering Content Services
Comment 5 Russell Dickenson 2011-08-30 04:54:21 UTC 
Release Notes Text: Added: CAUSE

CONSEQUENCE

FIX

RESULT
Comment 6 Jiri Skrabal 2012-11-13 15:56:51 UTC 
Release Notes Docs Status: Removed: Not Yet Documented 
Writer: Removed: ekopalov 
Release Notes Text: Removed: CAUSE

CONSEQUENCE

FIX

RESULT 
Docs QE Status: Removed: NEW
Comment 10 Weinan Li 2013-03-25 11:47:55 UTC 
We'll work on this for EWS 2.0.1
Comment 11 Jean-frederic Clere 2013-04-02 15:17:42 UTC 
The fix is r1137200 so fixed starting JK_1_2_32 so you just need to update mod_jk version.
Comment 12 Libor Fuka 2013-04-09 14:01:31 UTC 
We have mod_jk/1.2.36 in EWS 2.0.0 GA
Comment 13 John Doyle 2013-04-09 15:21:55 UTC 
If we have 1.2.36 in 2.0.0, is this actually an EWS 1 request?
Comment 14 Libor Fuka 2013-04-09 15:28:15 UTC 
the newest version of mod_jk is 1.2.37 and this version resolving our bug 900793
Comment 15 Permaine Cheung 2013-05-02 14:36:30 UTC 
mod_jk-1.2.37-1.redhat_1.ep6.el6 and mod_jk-1.2.37-1.redhat_1.ep6.el5 are built in Brew.
Comment 16 Mandar Joshi 2013-05-16 13:02:38 UTC 
@Wei Nan, can you provide CCFR for this bug?
Comment 17 Weinan Li 2013-05-17 05:26:37 UTC 
Release Notes Text: Added: 

CAUSE

We need to resolve bug 900793

CONSEQUENCE

mod_jk is 1.2.37 and this version resolves bz900793

FIX

Upgrade mod_jk to 1.2.37

RESULT

mod_jk upgraded to 1.2.37
Comment 18 Libor Fuka 2013-05-17 06:53:59 UTC 
Don't forget to apply patch from BZ https://bugzilla.redhat.com/show_bug.cgi?id=900793 above 1.2.37 version.
Mladen knows more info.
Comment 19 Mladen Turk 2013-05-17 07:04:36 UTC 
Yep there is patch inside windows/solaris branch which must be applied to RHEL branches as well
http://pkgs.devel.redhat.com/cgit/rpms/mod_jk/tree/tomcat-connectors-1.2.37-JBPAPP-9703.patch?h=jb-ep-6-xb

Weinan is this patch applied already?
Comment 20 Weinan Li 2013-05-17 13:10:54 UTC 
yes, the patch name is: tomcat-connectors-1.2.36-JBPAPP-9164.patch
Comment 21 Radim Hatlapatka 2013-05-22 15:40:44 UTC 
Verified for Windows and Solaris that it contains mod_jk 1.2.37
Comment 22 Radim Hatlapatka 2013-05-23 08:05:23 UTC 
Verified also for RHEL that the mod_jk version is 1.2.37
Comment 23 Mandar Joshi 2013-05-29 16:39:05 UTC 
Added DocText.

@Wei Nan Li, can you please review the Doc Text content?

Since bug 900793 is already documented, do we need to document this bug? This bug seems to be dependant/duplicate of bug 900793.
Comment 24 Weinan Li 2013-05-30 02:44:43 UTC 
Yeah, we need to document all the version changes of components.