That seems to be the case as I suspected, or at least the behaviour
described matches what I saw initially and looked to be resolved as
expected while trying out things with a modified hello_world.
Based on the docs at [1] I came up with connection options string
"{protocol:amqp1.0, container_id:myclientid}" to provide a specified
container-id for the connection. I had to add the protocol option as
well because although the client would be using AMQP 1.0 with Artemis
anyway, it first tries AMQP 0-10 for historic compatibility reasons
before doing so, and the container_id option is only applicable for
AMQP 1.0.
Separately, if you are just starting out on new development as it
appears I would suggest you also consider the Qpid Proton C++ client
binding as that is where more of the active development is these days
vs the older client.
[1]
http://qpid.apache.org/releases/qpid-cpp-1.39.0/messaging-api/cpp/api/classqpid_1_1messaging_1_1Connection.html#a4d3f1bacc02722f3d2ae43efaa880db6
Robbie
On Thu, 18 Jun 2020 at 10:53, Robbie Gemmell <robbie.gemm...@gmail.com> wrote:
>
> I actually think its possible that it is already creating a 'stable'
> name for the backing queue, but that your application is not fully
> supplying the same needed details on subsequent connection attempts.
>
> The backing queue name will be composed of details around both a
> 'client id' and a subscription name, and both must be given the same
> value on subsequent attempts to use an existing subscription. In AMQP
> terms for Artemis that's the client connection container-id and the
> link name respectively. You are specifying the link name, but I
> suspect you are not supplying a fixed container-id and so the client
> is generating one for you on each connection, causing an independent
> subscription to be created for the new client id.
>
> I'll have a play and see if I can confirm.
>
> Robbie
>
> On Thu, 18 Jun 2020 at 09:40, mohank <moha...@eventtracker.com.invalid> wrote:
> >
> > Hi,
> >
> > I am using below configuration
> > Broker : Activemq Artemis
> > Client : QPID C++( QPID Messaging APIS's for AMQP 1.0)
> >
> >
> > using QPID C++ mesaging api, I want to create Queue with stable name(ex :
> > my-subscription) and routing type as "Multicast"
> > I am using address : "'news.*'; {node: {type:topic, capabilities: [shared]
> > }, link:{durable:True, name:'my-subscription'}}"
> >
> > But result looks totally different, It creates Queue name with random name,
> > every time I start the application It creates new queue with random name and
> > with its options.
> > Find the below screenshot fro the same.
> >
> > <http://qpid.2158936.n2.nabble.com/file/t396514/Queue_table_using_QPID.jpg>
> >
> > I have tried with NMS API from activeMQ, It creates the stable Queue name
> > with multicast routing type, Every time when i restart application, It
> > utilize the existing queue Or it create if it doesn't exist.
> > <http://qpid.2158936.n2.nabble.com/file/t396514/Queue_table.jpg>
> >
> > Is it possible to create Queue with stable name and multicast routing key
> > using QPID C++ Messaging API ?
> >
> > Thanks,
> > Mohan
> >
> >
> >
> > --
> > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
