Bug 1158079 - (6.4.0) Upgrade to HornetQ 2.3.23.Final from 2.3.21.Final-redhat-1
Summary: (6.4.0) Upgrade to HornetQ 2.3.23.Final from 2.3.21.Final-redhat-1
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR8
: EAP 6.4.0
Assignee: Clebert Suconic
QA Contact: Miroslav Novak
URL:
Whiteboard:
: 1149121 (view as bug list)
Depends On: 1141873 1143818 1146506 1147382 1151466
Blocks: 1149127
TreeView+ depends on / blocked
 
Reported: 2014-10-28 14:00 UTC by Kabir Khan
Modified: 2019-08-19 12:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
// EAP6-332 - Ability to close all consumers on a destination and the connections for these consumers // Question - Is it necessary to add mention of the Management CLI command? The ability to close all consumers on a destination and the connections for those consumers has been added. This command is available via the Management CLI, management API and JMX. // EAP6-337 - Abort slow HornetQ consumers The rate of consumption for message consumers may now be monitored automatically, and action taken if the rate does not meet specific criteria. A minimum consumption rate is specified in messages per second and if it is not met, either the consumer's connection is killed or a management notification is raised, which can be handled by an application. By default this feature is disabled. // EAP6-331 - Ability to terminate a connection by JMS User HornetQ now supports termination of connections with the JMS user as the criteria. Previously it was only possible to terminate connections according to the client ID or IP address.
Clone Of:
Environment:
Last Closed: 2019-08-19 12:44:08 UTC
Type: Component Upgrade
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EAP6-331 0 Major Closed Ability to terminate a connection by JMS User 2018-05-31 00:57:32 UTC
Red Hat Issue Tracker EAP6-332 0 Major Closed Ability to close all consumers on a destination and the connections for these consumers 2018-05-31 00:57:32 UTC

Description Kabir Khan 2014-10-28 14:00:43 UTC
This upgrade is needed to backport features for the following two change requests:

https://issues.jboss.org/browse/EAP6-332 -> https://issues.jboss.org/browse/HORNETQ-1374
https://issues.jboss.org/browse/EAP6-331 -> https://issues.jboss.org/browse/HORNETQ-1373

Comment 1 Clebert Suconic 2014-10-29 21:28:10 UTC
I have created the tag HornetQ_2_3_22_Final


should I upload a regular one or you want a brewed build?

Can you assign someone who can do the proper build? if you need a regular build let me know and i will upload one real quick.

Comment 2 Kabir Khan 2014-10-30 00:02:06 UTC
Regular is fine until after dev freeze (25 Nov)

Comment 3 Clebert Suconic 2014-10-30 01:43:16 UTC
https://github.com/jbossas/jboss-eap/pull/1862

Comment 4 Clebert Suconic 2014-10-30 14:58:08 UTC
2.3.22 failed.. there was a test failure on it.. one of the committs didn't includ a proper fix.

Comment 5 Clebert Suconic 2014-10-30 19:29:08 UTC
https://github.com/jbossas/jboss-eap/pull/1866

Comment 6 Ivo Studensky 2014-11-05 09:01:13 UTC
*** Bug 1149121 has been marked as a duplicate of this bug. ***

Comment 7 Vladimir Dosoudil 2014-11-11 12:48:03 UTC
MEAD build: https://brewweb.devel.redhat.com/taskinfo?taskID=8223129
Prod rebuild PR: https://github.com/jbossas/jboss-eap/pull/1937

Comment 8 Miroslav Novak 2014-11-12 07:36:36 UTC
EAP 6.4.0.DR8/9 contains HornetQ 2.3.23.Final. Setting as verified.

Comment 10 JBoss JIRA Server 2015-04-28 15:03:55 UTC
John Doyle <jdoyle> updated the status of jira EAP6-331 to Closed


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