activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine Toulme <>
Subject Re: Problem with MQTT pattern subscription in a cluster
Date Sat, 15 Oct 2016 00:52:58 GMT
I have a test showing a cluster using MQTT, but it passes.

Either the test is bogus, the issue is intermittent, the issue was fixed since 1.4.0 and/or
my cluster configuration is wrong.

Previously, I have found the issue to be intermittent.

Please feel free to take a look at the test. If it looks of value, I can create a pull request
for it:

I’ll try to rerun my set up:
-with trace logging turned on
-with the latest code from master

Any help is very appreciated.



> On Oct 14, 2016, at 8:28 AM, Antoine Toulme <> wrote:
>> On Oct 14, 2016, at 3:01 AM, Martyn Taylor < <>>
>> As a quick check can you tell me what message-load-policy you have
>> configured on your cluster connection.  Could you try setting this to
> It was unset, I tried setting to STRICT. That didn’t change the behavior.
>> If that doesn't work a reproducer would be the best thing to provide.  I
>> can manage to get somewhere with the modified cluster test, send a PR and
>> I'll take a look.  If not let me know and I'll see if I can reproduce this
>> myself (it would help if you could send your broker config).
> I should have a test to share later today.
> In the mean time, my broker config is here:
> <>
> Both nodes use the same config, swapping <IP1> and <IP2> to point at each
>> Thanks
>> On Fri, Oct 14, 2016 at 8:39 AM, Antoine Toulme < <>>
>> wrote:
>>> Hello,
>>> we are trying out ActiveMQ Artemis with MQTT. We are interested in using
>>> pattern subscription such as foo/# to listen to a set of topics.
>>> We created a cluster in which one client publishes to a node, while an
>>> other one subscribes to another.
>>> When using pattern subscriptions, we see that the subscriber does not
>>> receive the message.
>>> When using an exact subscription (foo/bar), the subscriber receives the
>>> message.
>>> I tried to recreate the situation by modifying one of the clustering
>>> integration tests (MessageRedistributionTest). I’m not quite there yet
>>> mostly because of my ignorance of the internals.
>>> Are you aware of this issue? I’d be happy to show you my demo and the
>>> results. Also happy to share whatever code, however crappy, I have written
>>> to create a test for this so far.
>>> Cheers,
>>> Antoine

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message