You're right the problem was the > wildcard ... thank you !
Le mercredi 16 mars 2016 à 08:03 -0600, Quinn Stevenson a écrit :
> Looking at your sample, I think your destination name is causing you
> problems. The “>” character is for pattern matching in the configs
> and wildcard subscribers - I
Looking at your sample, I think your destination name is causing you problems.
The “>” character is for pattern matching in the configs and wildcard
subscribers - I don’t think wildcard producers are supported. Can you try it
with a different destination name? Anything other than “>”.
My sam
Thank you for the feedback.
I have created a simple test case for this based on one of the ActiveMQ basic
examples (attached to this mail - App.java).
I create two producers, one that will send messages to virtual topic
VirtualTopic.> and another
one that will send messages to virtual topic V
Is there a specific reason the default configuration won’t work for you?
(Either don’t set anything, or explicitly set the default of
I tried a simple sample using the defaults, and it seems to accomplish what
you’re after.
> On Mar 14, 2016, at 11:05 AM, Nuno Oliveira
> wrote:
>
> prefix
Hi,
I have a doubt regarding virtual topics and how the messages are routed
(replicated) to the consumers (queues).
I'm using two virtual topics one with the default name (VirtualTopic.>) and
another
one named VirtualTopic.MIGRATION.
I have three consumers (queues):
* Consumer.2b36ad7a-e641
