bootstrap.xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider Broker Connections 69 Mirroring The idea of mirroring is to send events that happen on a broker towards another broker, without blocking any operations from producers and Disaster Recovery, and depending on the requirements even for failing over the data. The following events are sent through mirroring: Message sending Messages sent to one broker will be "replicated" to

bootstrap.xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider Broker Connections 79 Mirroring The idea of mirroring is to send events that happen on a broker towards another broker, without blocking any operations from producers and Disaster Recovery, and depending on the requirements even for failing over the data. The following events are sent through mirroring: Message sending Messages sent to one broker will be "replicated" to

bootstrap.xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider Broker Connections 76 Mirroring The idea of mirroring is to send events that happen on a broker towards another broker, without blocking any operations from producers and Disaster Recovery, and depending on the requirements even for failing over the data. The following events are sent through mirroring: Message sending Messages sent to one broker will be "replicated" to

bootstrap.xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider connection can capture events from the broker and pass them over the wire to another broker. This enables you to capture multiple asynchronous replicas. The following types of events are captured: Message acknowledgement Queue and address creation queue and address deletion When you configure a mirror, these events are captured from the broker, stored on a local queue, and later forwarded to a target destination

bootstrap.xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider connection can capture events from the broker and pass them over the wire to another broker. This enables you to capture multiple asynchronous replicas. The following types of events are captured: Message acknowledgement Queue and address creation queue and address deletion When you configure a mirror, these events are captured from the broker, stored on a local queue, and later forwarded to a target destination

bootstrap.xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider reproduce any operation that happened on the source brokers towards a target broker. The following events are sent through mirroring: Message sending Messages sent to one broker will be "replicated" to entries used to govern which addresses (and related queues) mirroring events will be created for on this broker-connection. That is, events will only be mirrored to the target broker for addresses that match

bootstrap.xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider reproduce any operation that happened on the source brokers towards a target broker. The following events are sent through mirroring: Message sending Messages sent to one broker will be "replicated" to entries used to govern which addresses (and related queues) mirroring events will be created for on this broker-connection. That is, events will only be mirrored to the target broker for addresses that match

bootstrap.xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider reproduce any operation that happened on the source brokers towards a target broker. The following events are sent through mirroring: Message sending Messages sent to one broker will be "replicated" to entries used to govern which addresses (and related queues) mirroring events will be created for on this broker-connection. That is, events will only be mirrored to the target broker for addresses that match

bootstrap.xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider Broker Connections 78 Mirroring The idea of mirroring is to send events that happen on a broker towards another broker, without blocking any operations from producers and Disaster Recovery, and depending on the requirements even for failing over the data. The following events are sent through mirroring: Message sending Messages sent to one broker will be "replicated" to

bootstrap.xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider Broker Connections 78 Mirroring The idea of mirroring is to send events that happen on a broker towards another broker, without blocking any operations from producers and Disaster Recovery, and depending on the requirements even for failing over the data. The following events are sent through mirroring: Message sending Messages sent to one broker will be "replicated" to