Perfect! This works that I expected.
Thanks.
Juan Manuel
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-with-embedded-broker-tp4687370p4687404.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
You can specify that messages should be forwarded even if no consumer is
connected by using the staticallyIncludedDestinations element on the
networkConnector. See
https://access.redhat.com/documentation/en-US/Fuse_ESB_Enterprise/7.1/html/Using_Networks_of_Brokers/files/FMQNetworksMessagePropagati
This is by default? Can I change that?
What's the best architecture for a system that need send message to a remote
broker all the time and if the remote broker is offline, need to save this
message in a local queue and send when the connection is established again ?
--
View this message in cont
That's expected behavior. By default, brokers only forward messages when
there's a currently-connected consumer somewhere in the network. If
there's no consumer, the message will hang out on the producing broker,
waiting for the consumer to connect. When it does connect, the broker that
holds th
