Bug 1158079

// 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.