ActiveMQ and Artemis reliability - Messages lost

Hello everyone, As was recently mentioned [1], we started to analyze the currently used queue system. During the first iteration, we started to test reliability. Testing environment: AWS Hardware: | Producer | m5.large | 2vCPU / 8GiB | | Consumer | t3.medium | 2vCPU / 2GiB | Software: OS:

Re: ActiveMQ and Artemis reliability - Messages lost

Found a typo: Hardware: | ActiveMQ/Artemis| m5.large | 2vCPU / 8GiB | | Producer/Consumer | t3.medium | 2vCPU / 2GiB | Thank you! Slava. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: ActiveMQ and Artemis reliability - Messages lost

Tim, I'm not a developer at the moment... This is why I tried to find the right tool for such tests. I have tried more than 10 from the publicly accessible. And also asked in the initial post which tool may be used for such type of tests, maybe someone know a good one. Currently, for the tests,

Re: ActiveMQ Failover Transport for Artemis

Hello Art, Thank you for the reply! I'm also interested in how to specify two nodes for the end client. Assuming we have two servers: IP1, IP2. For ActiveMQ we may use it in the following way: failover:(tcp://IP1:61616,tcp://IP2:61616) Is there a way to specify two hosts when we connecting to

Re: ActiveMQ and Artemis reliability - Messages lost

jbertram, Almost all things were done using Ansible and shell script. 1. Ansible - Create AWS environment. 2. Ansible - Install AMQ/Artemis. 3. Shell - script for Jms Tools to produce the tests and generate the reports. 4. A line of code to restart systemd service. If you are interested, I may

Re: ActiveMQ and Artemis reliability - Messages lost

Hello Tim, Yes, you are right, thank you for observation! I've added one more line in the table - 'Messages remained'. During the test, each iteration uses its own queue name. The consumer is configured to consume all messages from the queue with a 30 seconds timeout. At the end of the test, I

Re: ActiveMQ and Artemis reliability - Messages lost

Reuploaded all 3 images because of overlaps in resulting filenames:

Re: ActiveMQ and Artemis reliability - Messages lost

Hello, Project with description and all required data for tests reproducing were posted on Github: https://github.com/veaceslavdoina/messages-brokers-testing The issue was raised in Jira: https://issues.apache.org/jira/browse/AMQ-7096 Slava. -- Sent from: http://activemq.2283324.n4

Re: ActiveMQ and Artemis reliability - Messages lost

The issue for Artemis was raised: https://issues.apache.org/jira/browse/ARTEMIS-2173 Slava. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: ActiveMQ and Artemis reliability - Messages lost

Hello, Added ActiveMQ test results using xa: https://github.com/veaceslavdoina/messages-brokers-testing/blob/master/RESULTS.md#test-activemq-5157-standalone-xa-20181114-090010 Slava. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: ActiveMQ and Artemis reliability - Messages lost

Justin, thank you for advice! Just run a test using a single instance for the broker and producer/consumer. All communication was done using localhost. Got similar results: https://github.com/veaceslavdoina/messages-brokers-testing/blob/master/RESULTS.md#test-artemis-263-standalone-local

ActiveMQ 5.x reliability and ActiveMQ Artemis questions

Hello everyone, We are started to investigate how our current messaging system configuration is fault-tolerant and highly available and we also investigating how we may increase its throughput. Currently, we use Apache ActiveMQ 5.14.3 in a Master/Slave configuration using JDBC Master Slave with