Matt Pavlovich
>
>> On Feb 22, 2024, at 8:20 PM, Bruce Cooper wrote:
>>
>> "static:failover:
>
fo
> 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 2
-system-master-slave
On Mon, 26 Feb 2024 at 10:00, Bruce Cooper wrote:
> 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 assistanc
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
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
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
