> On Oct 14, 2016, at 3:01 AM, Martyn Taylor <mtay...@redhat.com> wrote:
> 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 other.
> On Fri, Oct 14, 2016 at 8:39 AM, Antoine Toulme <antoine.tou...@gmail.com>
>> 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
>> 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.