The Camel example in the activemq-artemis-examples GIT repo still depends on
Camel 3.16.
However, Camel 3.x will become obsolete at the end of this year.
The supported Camel version is now 4.8.
Can someone update the example? Many thanks!
Erik
the bottom of the email. I
> recall encountering a similar issue in ActiveMQ classic so I just
> linked it there.
>
> Ken
>
> On Tue, Sep 17, 2024 at 2:16 AM Devriendt, Erik
> wrote:
>
> > Hello Ken
> >
> > Your link points to the documentation of the Activ
Hello Ken
Your link points to the documentation of the ActiveMQ Classic version.
Patrick indicates as version: AMQ: v2.36.0, which is the Artemis version.
I think a better link is
https://activemq.apache.org/components/artemis/documentation/latest/federation.html#federation
Anyhow, several mont
nd it looks like
>> it started failing in 2.32.0 when we moved from Jetty 10.0.15 to 10.0.16.
>> It appears that something changed in that version of Jetty to break the
>> code in Artemis responsible for restarting it.
>>
>>
>> Justin
>>
>> On Thu, A
Hello all
I first noticed the problem described below with Artemis 2.35.0, but version
2.37.0 shows the same behavior:
Calling the restartEmbeddedWebServer() operation via the web console does stop
jetty and tries to restart it but jetty then generates a lot of exceptions, and
the web console
We stumbled on an issue in Artemis with the handling of the TTL field of
received AMQP.
Our Artemis instance has a AMQP broker connection to a IBM MQ broker and
receives messages forwarded by that IBM MQ broker.
If the IBM client does not provide a specific TTL for a message, IBM MQ by
default s
Many thanks to those who replied to my question.
-Original Message-
From: Devriendt, Erik
Sent: 8 May, 2024 11:56
To: users@activemq.apache.org
Subject: MQTT retained messages and federation
Hello all
I have a question about retained messages in MQTT.
I have 2 federated activeMQ
Hello all
I have a question about retained messages in MQTT.
I have 2 federated activeMQ Artemis 2.32.0 brokers A and B.
When I start a MQTT client on broker A that publishes a retained message on a
given topic and then exits, a second MQTT subscriber client started later and
connected to that
Hello all
We plan to use ActiveMQ Artemis in a larger project for our customer.
This broker will serve the message exchange between the internal components of
our system, but the customer also asks to connect to their IBM MQ broker for
publishing data from the new system to other systems that ar
Herbert, you might try the hub and one of the spoke broker.xml that I posted in
this topic.
You should then publish and subscribe on topics with a name that starts with
‘cms’, if you don’t want to change the address-policy:
Better then also remo
BTW, as test producer and test consumer I used:
artemis consumer --destination="topic://cms.test"
artemis producer --destination="topic://cms.test"
I guess that attachments won’t work, so I include them as plain text.
BROKER A (a spoke)
http://www.w3.org/2001/XMLSchema-instance";
xmlns:xi="http://www.w3.org/2001/XInclude";
xsi:schemaLocation="urn:activemq
/schema/artemis-configuration.xsd">
I tried to set up a small Hub-Spoke topology of 3 Artemis brokers. Each on a
different machine, and expected to be able to configure address federation.
I have 3 brokers: A, B and C. If I configure them in a full mesh topology,
address federation works, that is, a consumer on any of the broker ma
13 matches
Mail list logo
