Este contenido no está disponible en el idioma seleccionado.
Chapter 3. New and Changed Features
This section describes a highlighted set of enhancements and changed features in AMQ Broker 7.13. For a full list of enhancements, see AMQ Broker 7.13.0 Enhancements
- FIPS tolerance
- AMQ Broker 7.13 is FIPS-tolerant, which means it automatically runs on a FIPS-enabled OpenShift cluster or RHEL system. One caveat is that the broker cannot use the default codec, org.apache.activemq.artemis.utils.DefaultSensitiveStringCodec, to encode passwords. The default codec uses the Blowfish algorithm, which is not FIPS-tolerant. The Blowfish algorithm is deprecated in 7.13. For more information, see Disabling FIPS mode in Deploying AMQ Broker on OpenShift and Disabling FIPS mode in Configuring AMQ Broker.
- JSON format support for brokerProperties
-
In 7.13, you can configure brokerProperties in JSON format. JSON format is more compact than text format for writing properties which means you can add more properties to an individual file without exceeding the 1 MB size limit for a properties file. For more information, see Segregating the
brokerPropertiesconfiguration in Deploying AMQ Broker on OpenShift. - New AMQ Management Console
In 7.13, the next generation AMQ Management Console based on HawtIO 4 is integrated with AMQ Broker. The previous HawtIO 2 console was based on the Bootstrap framework which is no longer supported by the Bootstrap foundation. The highlights of the new console include:
- Uses modern web technologies React and Patternfly.
- Has a faster and more responsive UI.
- Provides a cleaner separation between tabular views and JMX views.
- Supports generic OpenID authentication. OpenID Connect Core 1.0 is a widespread specification and standard method for distributed authentication (based on OAuth 2).
- Has an improved filterable broker diagram
NoteBy default, the new console throttles authentication to protect against brute force attacks. As a result, you might see an intermittent error 429 when logging in to the web console. If you want to disable throttle authentication:
-
On AMQ Broker on RHEL, add a new argument,
-Dhawtio.authenticationThrottled=false, to theJAVA_ARGSlist of Java system arguments in theartemis.profilefile. -
On AMQ Broker on OpenShift, add a Java environment variable and specify a value of:
-Ddhawtio.authenticationThrottled=false. For more information about setting environment variables, see Setting environment variables for the broker containers in Deploying AMQ Broker on OpenShift.
NoteIn HawtIO 4, the
hawtio.roleproperty is not supported. Therefore, you must use thehawtio.rolesproperty to grant one or more roles access to AMQ Management Console.- Percentage-based global memory limit
- In previous releases, it was possible to set a global memory limit for all addresses only as an absolute value. In 7.13, you can set the global memory limit value as a percentage of the maximum memory that is available to the broker JVM. For information, on OpenShift, see Configuring the maximum JVM memory available to a broker in Deploying AMQ Broker on OpenShift and on RHEL, see Configuring paging limits for all addresses in Configuring AMQ Broker.
- New metrics exposed by the AMQ Broker Prometheus plugin
In 7.13, the following new metrics are exposed by the AMQ Broker Prometheus plugin:
session_count: The number of sessions on this server.total_session_count: The total number of sessions created on this server since it was started.artemis_limit_percent. The percentage of a configured memory limit that is used by a specific address.- Log4J2
JsonTemplateLayoutsupport - You can change the default layout of the logs written by the Log4J logging utility to JSON Template Layout. For more information see Configuring logging in Configuring AMQ Broker.
- AMQ Core Protocol JMS client retry parameters
- In 7.13, the AMQ Core Protocol JMS client applies the values of the retryIntervalMultiplier and maxRetryInterval parameters to an initial connection attempt. In previous releases, the client used these parameters in reconnection attempts but not in an initial connection attempt.
- Consumer priority support for AMQP clients
- AMQ Broker 7.13 allows you to set consumer priority for AMQ clients, such as Red Hat build of Apache Qpid JMS.
- Red Hat Universal Base Image (UBI) 9 container images
- The AMQ Broker for OpenShift container images are built based on Red Hat UBI 9. UBI 9-based broker container images are compatible with RHEL8 host systems.
- Operator channels
A new Operator,
Red Hat Integration - AMQ Broker for RHEL 9 (Multiarch), is provided on OperatorHub for 7.13. Updates for this Operator are provided in the7.13.xchannel only. The7.13.xchannel is a Long Term Support (LTS) channel.A
7.12.xLTS channel provides updates for theRed Hat Integration - AMQ Broker for RHEL 8 (Multiarch) Operator. This channel is for version 7.12 only.NoteIt is not possible to upgrade the Operator by switching channels. You must uninstall the existing Operator and install the new version of the Operator from the appropriate channel.
To determine which Operator to choose, see the Red Hat Enterprise Linux Container Compatibility Matrix.
- Example programs
- In AMQ Broker 7.13, example programs are not distributed and installed with the broker. Instead, you can access the example programs in the following repository: https://github.com/apache/activemq-artemis-examples.