I looked at the jmstool, and I am not convinced of any bugs in Artemis and
AMQ. It uses an external logging mechanism to consider the state of
messages, which is likely not what will be in ActiveMQ or Artemis, nor may
it be truly representative of messages that have been passed (or not). What
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:
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
I strongly recommend you simplify your test for this. Whatever the issue
is (assuming an issue actually exists), it will need to be replicated with
a test in the Artemis test-suite (i.e. using one or more embedded brokers
on a single machine). I'd start with peeling back infrastructure layers
-20181112-172958
Provided playbooks can create a single instance with one Artemis broker:
Create an environment with one broker.
Install Artemis on the created instance.
Run test on the broker using localhost for producer/consumer.
The goal of the provided project is to permit an easy test results
My consumer is using MQTT, and I have multiple MQTT consumer instances which
work in loadbalance, if one of them consume the message is enough, others do
not need to consume again. It is said ActiveMQ virtual topic can be used to
distribute messages evenly among multiple consumers. ActiveMQ
