Chapter 1. Enhancements

  • ENTMQBR-2411 - Filtering based on AMQP message properties and annotations

    Before the broker moves an expired or undelivered AMQP message to an expiry or dead letter queue that you have configured, the broker now applies annotations and properties to the message. A client can use a filter based on these properties or annotations to select which messages to consume. For more information, see Filtering AMQP Messages Based on Annotations in Configuring AMQ Broker.

  • ENTMQBR-2736 - New resource audit logger

    AMQ Broker 7.7 adds a new resource audit logger. The resource audit logger logs events related to authentication, creation or deletion of broker resources from JMX or the AMQ management console, and browsing of messages in the management console. For more information, see Logging in Configuring AMQ Broker.

  • ENTMQBR-2919 - Setting ranges of message expiry values for addresses

    In AMQ Broker 7.7, you can specify minimum and maximum message expiry values for an address or set of addresses. For more information, see Configuring Message Expiry in Configuring AMQ Broker.

  • ENTMQBR-3046 - Performing broker health checks

    In AMQ Broker 7.7, you can use a command called artemis check to perform various health checks on a broker and its queues. For more information about the checks that you can run, use the help function. For example: 

    $ <broker-instance-dir>/bin/artemis help check

  • ENTMQBR-3134 - AMQ Broker OpenShift Operator: Configuring PVC size for broker deployments

    In AMQ Broker 7.7, you can use the Custom Resource (CR) instance for an Operator-based deployment to configure the size of the Persistent Volume Claim (PVC) required by brokers in the deployment for persistent storage. For more information, see Configuring broker storage requirements in Deploying AMQ Broker on OpenShift.

  • ENTMQBR-3573 - Configuring JVM metrics collection

    In AMQ Broker 7.7, you can configure the broker to capture standard sets of metrics relating to the host Java Virtual Machine (JVM) for the broker. Specifically, you can specify whether the broker captures JVM metrics for Garbage Collection (GC), memory, and threads. For more information, see Configuring the broker to collect JVM metrics in Managing AMQ Broker.

  • ENTMQBR-3746 - AMQ Broker OpenShift Operator: Configuring large message handling for AMQP messages

    In AMQ Broker 7.7, you can use the Custom Resource (CR) instance for an Operator-based deployment to configure large message handling for AMQP messages. For more information, see Configuring large message handling for AMQP messages in Deploying AMQ Broker on OpenShift.