I set up some docker images in this configuration as a preliminary step. One
oddity:
Configure 2.25 side not to run the reaper
Send message to 2.25 side
Observe that after expiry the message shows up in the expiry queue on the 2.20
side, but not on the 2.25 side, the message is removed from the
Hi John-
ActiveMQ 5.x runs great in Kubernetes. For Azure, the biggest performance piece
is the storage class used for the volume. You’ll want to measure throughput
using different storage classes to align your technical performance requirement
against cost tolerance of your cloud budget.
Hello,
We have a network of brokers in a hub/spoke setup
where each client (spoke) is configured with failover to the hub
(HOSTA/HOSTB) as follows:
The AMQ process on HOSTB is not available, we have external processes that
manage whether AMQ runs on HOSTA or HOSTB, but HOSTA
Hello James-
First thing— You have an inconsistent url — change "static:(failover:” to
uri=“masterslave:(tcp://hosta,tcp:hostb )” ..
Network Connectors imply failover and retry, and the ‘masterslave’ discovery
does a connect HOSTA, then HOSTB convention.
-Matt Pavlovich
> On Oct 12, 2022,
Greetings,
We aim to deploy AMQ “classic” or Artemis fairly soon into a cloud/Kubernetes
environment (Azure AKS initially), and I would ask for some guidance. Our
traffic is fairly low, like around 100 messages per second, but some of the
messages can be up to 1MB. The initial release will
is this the actual trace? or you cut some to post here?
Just puzzled by skipDelivery calling performAck..
artemis-test-artemis-1-m-1 |at
org.apache.activemq.artemis.protocol.amqp.connect.mirror.AMQPMirrorControllerTarget.lambda$performAck$2(AMQPMirrorControllerTarget.java:377)
Notice that main is now using SLF4j / log4j... (in case you manually
upgrade to a snapshot)
We are still working the details for an upgrade.
if you need to patch your 2.25.0 it's a straight change to make there
On Wed, Oct 12, 2022 at 9:52 PM Clebert Suconic
wrote:
>
> I don't know how I
Hey James,
For what it's worth... You can continue using static:(failover:(uri1, uri2))
with the addition of the following query params
"?randomize=false=0" which is functionally equivalent to
the "masterslave" protocol, e.g.:
static:(failover:(uri1,uri1)?randomize=false=0)
I have an
That’s the full output with regular logging levels. I can reproduce at will so
I have enabled trace level logging and pasted the result in
https://issues.apache.org/jira/browse/ARTEMIS-4045
Let’s take further discussion there?
From: Clebert Suconic
Date: Wednesday, October 12, 2022 at 9:10 PM
Having updated both sides to 2.25 I’m seeing this error in the logs, is it a
concern that warrants further investigation?
artemis-test-artemis-1-m-1 | 2022-10-12 22:01:43,632 ERROR
[org.apache.activemq.artemis.core.server] AMQ224041: Failed to deliver:
java.lang.IllegalStateException: this
I don't know how I would test it yet. It's fairly late in the night
for me.. I will think about it tomorrow.
but here is a tentative fix:
https://github.com/apache/activemq-artemis/pull/4256
On Wed, Oct 12, 2022 at 9:30 PM Stephen Baker
wrote:
>
> That’s the full output with regular logging
11 matches
Mail list logo
