Chapter 1. Enhancements

ENTMQBR-875 - Add support for retroactive addresses

AMQ Broker 7.6 adds support for retroactive addresses. Configuring an address as retroactive enables you to preserve messages sent to that address, including when there are no queues yet bound to the address. For more information, see Configuring Retroactive Addresses.

ENTMQBR-2188 - Support wildcards in role-based access control configuration

In AMQ Broker 7.6, when configuring the role-access element in your broker.xml configuration file, you can now use a wildcard expression in the key attribute of the match element. For more information, see Configuring Authentication Based on Roles.

ENTMQBR-2519 - Certification for Oracle 19c

AMQ Broker 7.6 adds support for Oracle Database 19c. Oracle Database 19c enables you to configure Oracle Real Application Clusters (RAC). RAC is an option for the Oracle Database that provides high availability (HA) and scalability to the Oracle Database without requiring any application changes.

For more information about the databases supported by different versions of AMQ Broker, see Red Hat AMQ 7 Supported Configurations. To learn more about Oracle RAC, consult the Oracle documentation.

ENTMQBR-2544 - Set LDAP connection timeout

In AMQ Broker 7.6, you can set timeouts for connection and read requests from the broker to an LDAP directory server. For more information, see Integrating with LDAP.

ENTMQBR-2755 - Support custom validation of TLS client certificates

In AMQ Broker 7.6, an administrator can specify an SSL TrustManagerFactory plugin in the broker configuration to associate with the SSL context. Specifically, a new configuration parameter, trustManagerFactoryPlugin can now be specified on an acceptor or connector. This option enables custom validation of TLS client certificates.

For more information, see Table A.3. Netty TLS/SSL Parameters in Appendix A. Acceptor and Connector Configuration Parameters.

ENTMQBR-2852 - Configurable page sync tiemout for AIO

If you are using AIO for journal-based persistence (that is, journal-type is set to ASYNCIO in your broker.xml configuration file), you can now use the page-sync-timeout configuration parameter to specify the page synchronization timeout duration.