![]() ![]() You can override the default behavior and specify different credentials to send individual messages. Starting in 7.11, messages are sent using the credentials that you use to log in to AMQ Management Console. In previous versions of AMQ Broker, it was necessary to specify a username and password in the AMQ Management Console Preferences page in order to send messages in AMQ Management Console. The credentials used to log in to AMQ Management Console are used to send messages By using these operations, you can avoid restarting AMQ Broker if, for example, you renew the SSL certificate for AMQ Broker. Starting in 7.11, you can stop and restart the embedded web server for AMQ Broker by using the stopEmbeddedWebServer, startEmbeddedWebServer and restartEmbeddedWebServer operations on the ActiveMQServerControl JMX MBean. Operations to control the embedded web server Therefore, configuration updates are applied when the broker reloads the configuration periodically, apart from any update that specifically requires a broker restart. A mutable secret can be updated without requiring a broker restart. In AMQ Broker 7.11 on OpenShift Container Platform, the configuration created by using the brokerProperties attribute in the CR is stored in a mutable secret. For more information, see Configuring a Pod disruption budget in Deploying AMQ Broker on OpenShift.īrokerProperties configuration is stored in a mutable secret In AMQ Broker 7.11 on OpenShift Container Platform, you can configure a Pod disruption budget to specify the minimum number of Pods in a cluster that must be available simultaneously during a voluntary disruption, such as a maintenance window. ![]() For more information, see Configuring broker connections in Configuring AMQ Broker. By using synchronous mirroring, you ensure that the mirrored broker is up-to-date for disaster recovery. Starting in 7.11, you can configure synchronous mirroring between brokers to ensure that messages are written to the volumes of both brokers in the mirror at the same time. For more information, see Restricting upgrades in Deploying AMQ Broker on OpenShift. Note that the upgrade attribute is deprecated in 7.11. You can uses these attributes to prevent automatic upgrades or permit upgrades only to specific versions or to a specific image. In AMQ Broker 7.11 on OpenShift Container Platform, you can use the image or version attribute in the main broker CR to control which container images are deployed. The image and version CR fields control container image deployment Java Authentication and Authorization Service (JAAS) login modules in a secret ![]() The brokerProperties element in the Custom Resource In AMQ Broker 7.11 on OpenShift Container Platform, the status information reported by the Operator in the main broker Custom Resource is extended to include the result of validation done by the Operator on configuration added using: For more information, see Restricting automatic upgrades in Deploying AMQ Broker on Openshift. You can configure the Custom Resource for your deployment to prevent automatic upgrades or to permit automatic upgrades only to specific versions or to a specific image. In AMQ Broker 7.11 on OpenShift Container Platform, the Operator automatically upgrades the broker container images to the latest available version. For more information, see Limiting disk usage during paging for specific addresses in Configuring AMQ Broker. In addition, you can limit the memory used to store paged messages that the broker transfers from disk back to memory when clients are ready to consume messages. If you configure AMQ Broker to page messages, you can limit the disk space used to page incoming messages to prevent the paging operation from using excessive disk space. For more information, see Configuring JAAS login modules in a secret in Deploying AMQ Broker on Openshift. In addition, you can configure login modules, such as LDAP, which are not configurable in the CR. By configuring JAAS login modules in a secret, you can update user and role information in properties files without needing to restart the broker. In AMQ Broker 7.11 on OpenShift Container Platform, you can configure JAAS login modules in a secret instead of using the ActiveMQArtemisSecurity CR to configure user authentication and authorization for AMQ Broker. Support for Java Authentication and Authorization Service (JAAS) login modules For more information, see Changing the logging level for the Operator in Deploying AMQ Broker on Openshift. In AMQ Broker 7.11 on OpenShift Container Platform, you can change the default logging level to increase or decrease the detail that is written to the Operator logs. You can customize the Log4j 2 logging configuration on both OpenShift Container Platform and RHEL platforms. Start in 7.11, AMQ Broker uses the Log4j 2 logging utility instead of the JBoss Logging framework to provide message logging. ![]()
0 Comments
Leave a Reply. |