Bug 1411738 - Please update tomcat to >= 7.0.70 to fix ASF Bugzilla – Bug 59619
Summary: Please update tomcat to >= 7.0.70 to fix ASF Bugzilla – Bug 59619
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tomcat
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Coty Sutherland
QA Contact: tomcat-qe
URL:
Whiteboard:
Depends On: 1414895
Blocks: 1414894
TreeView+ depends on / blocked
 
Reported: 2017-01-10 12:08 UTC by Miska Husgafvel
Modified: 2017-08-01 23:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 23:16:34 UTC

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


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2247 normal SHIPPED_LIVE Low: tomcat security, bug fix, and enhancement update 2017-08-01 19:43:19 UTC
Apache Bugzilla 59619 None None None 2017-01-10 12:08:08 UTC

Description Miska Husgafvel 2017-01-10 12:08:08 UTC 
Description of problem:

I have a Shibboleth IdP installation on CentOS Linux release 7.3.1611 (Core). After updating tomcat from 7.0.54-8.el7_2 to 7.0.69-10.el7 I started experiencing the issue described in https://bz.apache.org/bugzilla/show_bug.cgi?id=59619 . According to the bug report in ASF Bugzilla the issue is fixed in version >= 7.0.70. Would it be possible to update tomcat to version >= 7.0.70?


Version-Release number of selected component (if applicable): 7.0.69-10.el7


How reproducible:
Not reproducible trivially, requires installation and configuration of Shibboleth IdP.


Steps to Reproduce:
1. yum install tomcat
2. Install and configure Shibboleth IdP
3. systemctl start tomcat.service


Actual results:

Tomcat fails to start Shibboleth IdP container.


Expected results:

Shibboleth IdP container starts.
Comment 6 errata-xmlrpc 2017-08-01 23:16:34 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://access.redhat.com/errata/RHSA-2017:2247
Note You need to log in before you can comment on or make changes to this bug.