Bug 1610355 – [GSS](6.4.z) Upgrade HornetQ from 2.3.25.SP24 to 2.3.25.SP28

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1610355 - [GSS](6.4.z) Upgrade HornetQ from 2.3.25.SP24 to 2.3.25.SP28

Summary:	[GSS](6.4.z) Upgrade HornetQ from 2.3.25.SP24 to 2.3.25.SP28

Status:	CLOSED ERRATA

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Build (Show other bugs)
Sub Component:
Version:	6.4.20
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	CR1
Target Release:	EAP 6.4.21
Assigned To:	Radovan STANCEL
QA Contact:	Peter Mackay
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1532614 1603973 1609964 1610340 1610342 1610351 1613494
Blocks:	eap6421-payload
	Show dependency tree / graph

Reported:	2018-07-31 09:29 EDT by Brad Maxwell
Modified:	2018-09-24 17:47 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-09-24 17:47:22 EDT
Type:	Component Upgrade
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2018:2740	None	None	None	2018-09-24 17:47 EDT

Groups: None (edit)

Description Brad Maxwell 2018-07-31 09:29:11 EDT

Comment 13 errata-xmlrpc 2018-09-24 17:47:22 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.

https://access.redhat.com/errata/RHSA-2018:2740

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