Are you looking for your queue and addresses not to match? Are you
planning to pre-configure the queues in the broker config or not? The
below makes it seem like you pre-configured the queue in broker.xml
but im not sure, as the client config suggests you desire otherwise.
Note that the 'create:receiver ' option stuff in your client 'address'
config will likely have no effect against Artemis since it doesn't
know about the bits that will go along with that (for AMQP 1.0, I
think only the Qpid C++ broker probably does). The broker will just
regardless either auto-create what it needs (as it can out of the box)
or match up to a pre-defined queue if one exists. A lot of the client
'address string' syntax and client behaviours wont necessarily work
the same against Artemis as they might against the Qpid C++ broker,
some of those are specific/tuned to it.
I dont actually think that [client-side] address string will end up
working with a queue named "Test" either, unless there is some broker
config influencing it to, I think it might end up just using a queue
also named "testqueue.#" as well that the broker auto creates. The
options are a bit of a mish mash of queue and topic subscription
config. In which case maybe it stored your previously-configured
broker.xml max consumer config while auto-creating a queue and will
retain that until recreated (e.g delete it via the UI, or empty the
data dir to clear the journal based config).
Note that Artemis also has its own 'FQQN' syntax of
"AddressName::QueueName" that you might be able to leverage with the
old C++ client to get behaviours you want in other ways, if you do
want different address and queue names and the queues already exist,
e.g, just using something like "testqueue.#::Test;
{link:{filter:{name:jms-selector,
descriptor:'apache.org:selector-filter:string', value :
'AppID=AppID1'}}}" as the client 'address' string might work for that
style. Disclaimer: not tried most of this.
Robbie
On Fri, 7 Aug 2020 at 11:13, mohank <[email protected]> wrote:
>
> Hi,
>
> I want to create durable queue to consume data from multiple consumer
> applications using there filters.
>
> Using :
> Broker : ActiveMQ Artemis
> Client : QPID Messaging C++
>
> using the address
> testqueue.#; {create: receiver, link: {durable:True, name: 'Test',
> filter:{name:jms-selector, descriptor:'apache.org:selector-filter:string',
> value : 'AppID=AppID1'}}}
>
> In broker, Creating a Durable name "Test" and address "testqueue.#" and Max
> Consumers = 1.
>
> If more than one Consumers are trying to connect Queue, throwing exception
> "Unable to recreate subscription, consumers already exist"
>
> I have tried updating the broker.xml max-consumer count to some number in
> ActiveMQ Artemis, but after running the client application max consumers
> updated to 1 in console.
>
> Can someone suggest me how can I create Durable Queue, to consumer from
> multiple consumer with filters.
>
> Thanks,
> Mohan
>
>
>
>
>
> --
> Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
