[ 
https://issues.apache.org/jira/browse/ARTEMIS-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16636017#comment-16636017
 ] 

Pawel edited comment on ARTEMIS-2103 at 10/3/18 7:03 AM:
---------------------------------------------------------

Second consumer has the same name, because we have many consumers in single 
application and name is related to hostname/container name. Because we have 
separate handlers for different virtual topics, we can't use wildcard.

Our goal is to replace ActiveMQ with Artemis (because of HA) without 
application code modification.


was (Author: pawelj):
Second consumer has the same name, because we have many consumers in single 
application and name is related to hostname/container name. Because we have 
separate handler for different virtual topics, we can't use wildcard.

Our goal is to replace ActiveMQ with Artemis (because of HA) without 
application code modification.

> VirtualTopic doesn't work correctly with multiple consumers
> -----------------------------------------------------------
>
>                 Key: ARTEMIS-2103
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2103
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker, OpenWire
>    Affects Versions: 2.6.3
>            Reporter: Pawel
>            Priority: Major
>
> It's impossibe to subscribe multiple virtual topics with the same consumer 
> name.
> I've configured acceptor like described in documentation:
> {code:java}
> tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;virtualTopicConsumerWildcards=Consumer.*.%3E%3B2{code}
> When I'm connecting first consumer:  
> *Consumer.cons1.VirtualTopic.t1*
> proper binding is created.
> Next I'm trying to connect second consumer with the same name:
> *Consumer.cons1.VirtualTopic.t2*
> But no binding is created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to