Yes, that works for me!
Thank-you so much for your help!
On Mon, Dec 11, 2017 at 9:43 PM, Gordon Sim <g...@redhat.com> wrote:
> On 09/12/17 02:20, Michael Arnold wrote:
>
>> Thanks for the help - but am still stuck:
>>
>> 1. Added in a link name as follows:
>> string ReceiverAddress = "Topic.Subtopic/Subject; {create: always,
>> node:{type: topic, durable: true}, link:{reliability: at-least-once,
>> durable: true, name: subscription-name}}";
>> Messages are still lost
>>
>>> qpid-config list queue
>>>
>> Does not show 'subscription-name'
>> Also tried setting a link name on the SenderAddress (both the same and
>> different to the receiver name), without success
>> Also tried the following, without success
>> string ReceiverAddress = "Topic.Subtopic/Subject; {create: always,
>> node:{type: topic, durable: true}, link:{reliability: at-least-once,
>> durable: true, name: 'subscription-name', x-declare:{auto-delete:false}}
>> }";
>>
>> 2. Tried to enable AMQP1.0, but always get 'Failed with: Invalid URL' at
>> run-time. Tried the following:
>> Connection QPIDConnection(string("localho
>> st:5672?protocol='amqp1.0'"));
>> Connection
>> QPIDConnection(string("localhost:5672?protocol='amqp1.0'&
>> container_id='ABC123'"));
>>
>
> The options are passed in a a separate map (or string representation of
> map).
>
> the following results in 'Failed with: Invalid option: protocol not
>> recognised'
>> QPIDConnection.setOption("protocol", string("amqp1.0"));
>>
>> Could you please elaborate further?
>>
>
> The attached test, when built against 1.36, works for me. If I start the
> test program, then kill it and run qpid-stat -q I see
> my-client_subscription-name listed. (If I don't use 1.0, I see
> subscription-name as the queue).
>
> Does this work for you?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
