Este contenido no está disponible en el idioma seleccionado.
Chapter 4. Deprecated features
This section describes features that are supported, but have been deprecated from AMQ Broker.
- Two-way algorithm of the default codec
-
Starting in 7.13, the two-way algorithm of the default codec,
DefaultSensitiveStringCodec, is deprecated. ActiveMQArtemisAddressCRD-
Starting in 7.12, the
ActiveMQArtemisAddressCRD is deprecated. Use thespec.brokerPropertiesattribute in theActiveMQArtemisCR to create addresses and queues for your deployment. ActiveMQArtemisSecurityCRD-
Starting in 7.12, the
ActiveMQArtemisSecurityCRD is deprecated. Use thespec.brokerPropertiesattribute in theActiveMQArtemisCR to configure security for your deployment. ActiveMQArtemisScaledownCRD-
Starting in 7.12, the
ActiveMQArtemisScaledownCRD is deprecated. TheActiveMQArtemisScaledownCRD is used internally by the broker, so this change is transparent to AMQ Broker administrators. - Connection pooling for LDAP queries
-
Starting in 7.12, the
connectionPoolparameter, which enables connection pooling for LDAP queries, is deprecated. The built-in authorization and authentication caches provide an alternative way to optimize the performance of LDAP queries. For information on customizing the built-in caches, see Configuring authentication and authorization caching. upgradeattribute in Custom Resource-
Starting in 7.11, the
upgradeattribute and the associatedenabledandminorattributes are deprecated because they cannot work as originally designed. Use theimageorversionattributes to deploy specific broker container images. queuesconfiguration element- Starting in 7.10, the <queues> configuration element is deprecated. You can use the <addresses> configuration element to create addresses and associated queues. The <queues> configuration element will be removed in a future release.
- getAddressesSettings method
- Starting in 7.10, the getAddressesSettings method, which is included in the org.apache.activemq.artemis.core.config.Configuration interface, is deprecated. Use the getAddressSettings method to configure addresses and queues for the broker programatically.
- OpenWire protocol
- Starting in 7.9, the OpenWire protocol is a deprecated feature. If you are creating a new AMQ Broker-based system, use one of the other supported protocols. Starting with the 8.0 release, the Openwire protocol will be removed from AMQ Broker.
- Adding users when broker instance is not running
- Starting in 7.8, when an AMQ Broker instance is not running, the ability to add users to the broker from the CLI interface is removed.
- Network pinger
- Starting in 7.5, network pinging is a deprecated feature. Network pinging cannot protect a broker cluster from network isolation issues that can lead to unrecoverable message loss. This feature will be removed in a future release. Red Hat continues to support existing AMQ Broker deployments that use network pinging. However, Red Hat no longer recommends use of network pinging in new deployments. For guidance on configuring a broker cluster for high availability and to avoid network isolation issues, see Implementing high availability in Configuring AMQ Broker.
- Hawtio dispatch console plugin
-
Starting in 7.3, AMQ Broker no longer includes the Hawtio dispatch console plugin,
dispatch-hawtio-console.war. Previously, the dispatch console was used to manage AMQ Interconnect. However, AMQ Interconnect now uses its own, standalone web console.