You are welcome =)
failover - client side to support auto-reconnect to one or more brokers due to
connection drop
masterslave - broker side to support exactly your architecture. Moving messages
to one of a group of brokers where there is one active and one or more failover
brokers
Matt Pavlov
Hi Matt,
Thank you sooo much for answering my question. That simple config change fixed
the problem! I’m so grateful
Out of curiosity, the documentation mentions
but there are a some other non-intuitive options that must be configured for it
to work as desired
For my own edification, is the
Hi Bruce-
Network Connectors retry or ‘failover’ automatically, so you should don’t use
the ‘failover’ transport in your networkConnector uri.
The networkConnector uri scheme you are looking for in this architecture is
‘masterslave’:
https://activemq.apache.org/components/classic/documentation
Hi Marco,
Thanks for checking back in.
from pom.xml
org.apache.activemq
activemq-client
5.15.8
org.apache.activemq
activemq-pool
5.15.8
The server is 5.17.6
When you asked this, I realised my dependencies were kind of old, so I
updated it to
jakarta.jms
jakarta.jms-api
3.1.0
org.apa
Hello Bruce,
thanks for sharing precise info
That sounds really very strange and sounds like a bug of AMQ (or a
configuration issue).
A question, maybe trivial: which version of AMQ jar library are you using
on your Java producer?
*Distinti Saluti / *Kind Regards
M.G.
Il giorno lun 26 feb 202
Now I have to rescind my previous comments. It runs out NON_PERSISTENT
messages from clients or the browser console are forwarded and consumed
correctly, but PERSISTENT messages are not transmitted correctly. This is
true whether I send from the console, from JAVA using the JMS/OpenWire
client or
As a follow up, I can now confirm that using a different client (an AMQP
client written in javascript using the rhea library) works as expected. It
is just this Java process that is broken. Any assistance you can provide
would be greatly appreciated.
On Mon, 26 Feb 2024 at 09:21, Bruce Cooper w
Hi Marco,
Thanks for your response. I agree it is strange. I now have some more
information to share. It now looks like it has something to do with my
message producer, rather than core ActiveMQ behaviour.
If I send messages using the ActiveMQ console on Broker A, they are
transmitted and rece
Hello Bruce,
that sounds very strange because with BrokerB stopped I understood that
everything is working good at the first subsequent run of the producer
script
"
*5. Run the producer script again.6. Observe that one set of messages is
delivered*"
while the issue appears at the following run
Bruce Cooper"
An: users@activemq.apache.org
Datum: 23.02.2024 03:24
Betreff:[Ext] Issue with network of brokers and active/passive
pair
Hi,
I'm running into a strange issue configuring activemq 5.17.6 to forward
messages from a satellite broker to a pair of broker
Hi,
I'm running into a strange issue configuring activemq 5.17.6 to forward
messages from a satellite broker to a pair of brokers running in an
active/passive (failover) pair. I'm hoping somebody here can help me
I have three brokers. The first is running stand-alone, and is configured
with a o
11 matches
Mail list logo
