Use two simplex connections, and only set staticallyIncludedDestinations on
the hub side. Then messages will go to the hub and stay there, until
consumers connect to the hub to consume them. If instead they'll be
connecting to spoke brokers, then you need to read the Stuck Messages
section of the
I don't understand why setting networkTTL to 3 from 1 would make a
difference in a 2-broker NoB, and I don't see why the behavior would change
depending on whether you use a duplex connection or two simplex ones.
Seems fishy to me.
On May 11, 2016 8:18 AM, "exabrial" wrote:
> I think I figured th
Hi,
I have a HA cluster with one master and one slave. I am creating connection
factory with below settings.
HashMap map = new HashMap();
map.put("host", "artemis01-mydev");
map.put("port", "61616");
map.put(TransportConstants.SSL_ENABLED_PROP_NAME, true);
A consumer will be registered for each end of the network connector (that's
how the messages are received by the brokers).
If staticallyIncludedDestinations are used then messages will always be
send to the remote brokers even if there are no registered consumers. If
you use dynamicalyIncludedDes
I'm creating a hub-spoke network of brokers. I'd like the edge brokers to
forward their messages to the hub so I don't have a ton of small backing
stores of messages hanging around.
So on the "spoke" broker, I have this network connector:
I have tried to replace the JBoss TX manager by Atomikos and the behavior is
the same, so it's not a problem related to JBoss.
Does anyone use XA transaction with durable subscribers?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JTA-with-durable-topic-tp4711549p47118
I think I figured this out, how to increase networkTtl to 3
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-Duplex-Network-connector-only-creating-bridge-on-initiating-side-tp4711821p4711830.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hello everyone,
I'm trying to create a Network Of Brokers, preferably with a single duplex
connection. I *can* get this to work if I use network connectors and
listeners on each side, but that is not desirable for our deployment.
Here is broker 1, the one initiating the outbound duplex connectio
