activemq-artemis

Error “Invalid broker URL” while bridging ActiveMQ Artemis 7.4 with Weblogic 12.x

别等时光非礼了梦想. 提交于 2021-02-10 06:20:08
问题 I am trying to create bridge between Oracle 12.x and Redhat ActiveMQ Artemis 7.4. This is what has been done to set up the bridge: Set artemis-jms-client-all-2.9.0.redhat-00005.jar to WL classpath Set the following properties to WL classpath: java.naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory connectionFactory.ConnectionFactory=amq.xaqcf.myqueue queue.queues/myqueue=myqueue However, I get the following error: java.lang.Exception: javax.resource

Apache ActiveMq Artemis client reconnecting to next available broker in clustered HA replication/shared-data store

ε祈祈猫儿з 提交于 2021-02-05 11:40:29
问题 Broker.xml (host1) and host2 just the port number changes to 61616 and slave as configuration. In reference with Apache Artemis client fail over discovery <?xml version="1.0" encoding="UTF-8" standalone="no"?> <configuration xmlns="urn:activemq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd"> <core xmlns="urn:activemq:core"> <bindings-directory>./data/bindings</bindings-directory> <journal-directory>./data/journal<

Performance issues with ActiveMQ Artemis and Spring JmsTemplate

核能气质少年 提交于 2021-01-29 08:14:54
问题 While doing some load tests with the ActiveMQ Artemis broker and my Spring Boot application I am getting into performance issues. What I am doing is, sending e.g. 12,000 messages per second to the broker with JMSeter and the application receives them and saves them to a DB. That works fine. But when I extend my application by a filter mechanism, which forwards events after saving to DB, back to the broker using jmsTemplate.send(destination, messageCreator) it goes very slow. I first used

apache-artemis 2.13.0 - why broker issues AM1212037 connection failure and AMQ214013 Failed to decode packet message in ogs

此生再无相见时 提交于 2021-01-28 23:00:58
问题 I have setup the Aretmis in HA configuration (one node as master and another as backup in different VMs) From logs, i see the backup is announced, the configuration is similar to the config When clients connecting to the Broker from multiple VMs, i notice the broker (master) logs is displaying the below message more often. I see some anonymous nodes i sending some message which is not able to decode. but not sure how to debug or resolve it exactly. Key config is: i am using <acceptor name=

apache-artemis 2.13.0 - why broker issues AM1212037 connection failure and AMQ214013 Failed to decode packet message in ogs

為{幸葍}努か 提交于 2021-01-28 22:44:01
问题 I have setup the Aretmis in HA configuration (one node as master and another as backup in different VMs) From logs, i see the backup is announced, the configuration is similar to the config When clients connecting to the Broker from multiple VMs, i notice the broker (master) logs is displaying the below message more often. I see some anonymous nodes i sending some message which is not able to decode. but not sure how to debug or resolve it exactly. Key config is: i am using <acceptor name=

Apache Artemis Master-Slave Configuration: RAM consumption increases continuously up to 100% RAM usage - after that Broker stops working

和自甴很熟 提交于 2021-01-28 12:13:04
问题 I have a problem with the artemis failover cluster (master-slave configuration) and do not find an answer what I am doing wrong. My systems are two Ubuntu Linux 18 VM's with 4 Cores, 16GB RAM and 120 GB SSD and I use apache-artemis-2.11.0 with java version 1.8.0_111. I configured "-Xmx14G" in the artemis.profile file to give the artemis enough memory to run. JAVA_ARGS=" -XX:+PrintClassHistogram -XX:+UseG1GC -Xms512M -Xmx14G -Dhawtio.realm=activemq -Dhawtio.offline=true -Dhawtio.role=amq

How to get queue size (depth) in Artemis

一个人想着一个人 提交于 2020-12-15 06:39:22
问题 Using a Java client API, how can I get the queue size in a remote ActiveMQ Artemis 2.4.0 broker? 回答1: Such feature as stats belongs to the management API. It can be accessed over HTTP (jolokia), JMX or JMX via the messaging API. There is an example in the official documentation for users persistent enough to read it. I will recite it here for convenience. ClientSession session = ... ClientRequestor requestor = new ClientRequestor(session, "activemq.management"); ClientMessage message =