I’ve got an issue connecting to an ActiveMQ Artemis cluster (AMQ from Red Hat in fact) through Spring’s DefaultJmsListenerContainerFactory. DefaultMessageListenerContainer makes use of only one connection, regardless of the number of consumers you specify through the concurrency parameter. The problem is that, in the cluster, there are 3 brokers configured at the moment (and, as a dev, I shouldn’t care
Tag: activemq-artemis
ActiveMQ Artemis prefixes “jms.topic.” to all topic names defined on Spring Boot Client
I’m using ActiveMQ Artemis 2.18.0 and version 2.5.5 of the spring-boot-starter-artemis dependency on a Spring Boot client. In my use case clients are required to communicate with each other via topics. The issue is that the string jms.topic. is getting prefixed to every topic defined on the client. For example the topic foo.sendInfo becomes jms.topic.foo.sendInfo. The broker.xml file is as
Messages not consumed when using wildcard queues in ActiveMQ Artemis
If I create queues on ActiveMQ Artemis test.A and a wildcard queue test.# then I can send a message to test.A and it will also be delivered to test.#. However, I am surprised to learn that when I consume the message from test.# then the message is still present on test.A How can I change my code or configuration to
ActiveMQ Artemis queue deleted after shutdown of consuming client
I am newbie on JMS and ActiveMQ Artemis, and I have the following problem. I put a message in a requests queue normally from an application producer: After that from other application consumer I tried to consume that message. That works without problems. But when I shutdown the application consumer the request queue was deleted for no reason. My application
Configuring Boomi JMS connector to ActiveMQ Artemis
I’ve been using a JMS connector in Boomi to connect with ActiveMQ Artemis 2.14, but using the client library activemq-all-5.15.11.jar and factory org.apache.activemq.jndi.ActiveMQInitialContextFactory This works, except I’m having issues with the connections creating numerous org.apache.activemq.artemis.core.server.impl.MessageReferenceImpl objects in the heap, which aren’t associated with the actual messages, but rather the ActiveMQ.Advisory.TempQueue. So I’m trying to setup a Boomi JMS connector using
JMS client to ActiveMQ at server on Red Hat JBoss EAP 7.3 in Java
I am writing a Java client to connect to my JBoss EAP 7.3 server running ActiveMQ, and I am getting various connection responses as I alter the parameters. Please help me correct the parameters/code. I get: This is the Java client code in a try catch block attempting to connect: And these are my JNDI tree values in the EAP
Connection refused when trying to connect to ActiveMQ Artemis deployed on Openshift
We have an Openshift project ( project1 ) in which we setup an AMQ Artemis broker using the image : amq- amq-broker-7-tech-preview/amq-broker-71-openshif . Being the basic image we don’t have any configuration such as SSL or TLS. In order to do the setup we used as example : https://github.com/jboss-container-images/jboss-amq-7-broker-openshift-image/blob/amq71-dev/templates/amq-broker-71-basic.yaml After the deployment of the image on Openshift we have the