Hi,
I’m not sure if I have discovered a bug in Artemis (2.31.2) or if I have
misunderstood something.
I used the following command to create a new instance:
apache-artemis-2.31.2/bin/artemis create --user admin --password admin
--no-autocreate --require-login myBroker
I have added the
Hi,
We are replacing an old (5.9) remote ActiveMQ Classic broker with a remote
Artemis broker and have a few questions.
1. The Artemis broker is configured to persist messages in a database. Does
e.g. and have any effect at all when using a
database? Which configurations are not relevant
Hi,
Many unexpected things occured today but I managed to perform a very quick test.
I replaced the ra.xml only since I use a remote broker. I deployed the modified
activemq-rar.rar on a Wildfly 29 without any problems. I also deployed a MDB
which was able to consume a message from a queue on
Thanks for the response.
I'll try to test with the suggested ra.xml tomorrow.
Regards,
Calle
Hi,
Should it be possible to use any of the new resource adapters
activemq-rar-5.18.3.rar or activemq-rar-6.0.0.rar on a Jakarta EE 10 server?
I did a simple test by placing the files in the deployments directory on a
Wildfly 28 server (since that is how the resource adapter is deployed on my
Thanks for your suggestion and the comment regarding send-to-dla-on-no-route.
I will probably use your approach. However, I did try to do a little adjustment
by defining the DLQ address like this (since that appears to be similar to how
auto-create-dead-letter-resources creates queues when set
I finally managed to understand why I got the problems described earlier.
The "producer" uses "artemis-jms" while the deployed MDB uses "artemis-ra".
Both components uses
org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.createQueue(…).
However, "artemis-ra" tries to create the
Is there anyone who got any thoughts regarding the described behavior? Or is
there anyone who has made a similar migration and want to share some
suggestions?
Regards,
Calle
Från: Calle Andersson
Skickat: måndag, oktober 16, 2023 10:42:33 PM
Till: users
I have an old A-MQ with a lot of composite queues, e.g:
Currently, I'm investigating how to migrate to Artemis. The implementations of
the existing clients (which sends and receives messages) should not be adjusted
(i.e. the names of the queues should be the same and the clients should
I tried to deploy a MDB to a Wildfly 28 server but I still get the same
problems (however, the logging looks a little bit different on this server).
This was added to standalone-full.xml:
...
Thanks for the reply,
However, I had alread added it to my acceptor before my failing attempts:
Thanks for the reply,
I'm using ActiveMQ Artemis 2.31.0 as well.
Thanks for the suggestion on using the "consumer" and "producer" commands (I
didn't know of them). However, when using the commands everything worked as
expected (using my intended Artemis configuration).
I assume my problem
Hi,
Is there anyone who could confirm if it is possible to configure Artemis in the
same way as I explained in my previous mail or if I have misunderstood the
whole things.
Thanks in advance,
Calle
Från: Calle Andersson
Skickat: torsdag, oktober 5, 2023 1:55
Hi,
I've just started to investigate how Artemis works and I have some questions
regarding auto-creation of addresses/queues.
I don't want to allow any clients/servers (who sends and/or consumes messages)
to be able to auto-create addresses or queues. However, I want the broker to be
able to
for Jakarta EE 10 servers
Hi Calle-
The nextrelease of ActiveMQ 5.x will have full jakarta support, including the
resource adapter. Stay tuned.
Thanks,
Matt Pavlovich
> On Sep 15, 2023, at 3:32 AM, Calle Andersson
> wrote:
>
> I have an application which currently communicates with a
I have an application which currently communicates with an old remote ActiveMQ
“Classic” 5.9 using the resource adapter (activemq-rar.rar). I need to migrate
the application to an Jakarta EE 10 server (Wildfly) but the resource adapter
doesn’t seem to work on that server. Which options do I
16 matches
Mail list logo