Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1079896 - RHEL6 RPMs: Upgrade jgroups to 3.2.13.Final
RHEL6 RPMs: Upgrade jgroups to 3.2.13.Final
Status: CLOSED ERRATA
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: RPMs (Show other bugs)
6.3.0
Unspecified Unspecified
unspecified Severity unspecified
: ER2
: EAP 6.3.0
Assigned To: Yong Yang
Katerina Odabasi
: Rebase
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-24 05:12 EDT by Yong Yang
Modified: 2017-10-09 20:20 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-08-06 11:08:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:1020 normal SHIPPED_LIVE Important: Red Hat JBoss Enterprise Application Platform 6.3.0 update 2014-08-06 15:03:06 EDT

  None (edit)
Description Yong Yang 2014-03-24 05:12:42 EDT
Required upgrade.
Comment 1 Yong Yang 2014-03-25 02:02:04 EDT
Source URL: git://git.app.eng.bos.redhat.com/JGroups.git#ea7de18f37e6d2661e94a6b4d9af70bc972030aa
Mead-Build: org.jgroups-jgroups-3.2.13.Final_redhat_1-1
Brew-Build: jgroups-3.2.13-1.Final_redhat_1.1.ep6.el6
Comment 3 Katerina Odabasi 2014-07-31 12:24:23 EDT
Verified in EAP 6.3.0.ER10.
Comment 5 errata-xmlrpc 2014-08-06 11:08:44 EDT
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.

http://rhn.redhat.com/errata/RHSA-2014-1020.html

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