I have found the answer:
It is not possible to create durable subscriptions dynamically with
QPid/AMQ v1.0 due to:
Unsupported features and restrictions
The following restrictions exist when using JMS over AMQP 1.0 with Service
- Only one MessageProducer or MessageConsumer is allowed per Session. If
you need to create multiple MessageProducers or MessageConsumers in an
application, create a dedicated Session for each of them.
- Volatile topic subscriptions are not currently supported.
- MessageSelectors are not currently supported.
- Temporary destinations, i.e., TemporaryQueue, TemporaryTopic are not
currently supported, along with the QueueRequestor and TopicRequestor APIs
that use them.
- Transacted sessions and distributed transactions are not supported.
If required then need to use Azure SB API
On Tue, Aug 8, 2017 at 2:09 PM, 4 Integration <4integrat...@gmail.com>
> On the topic defined in Azure Service Bus "test.topic" I have a static
> subscription defined named "sub1".
> When publishing I use:
> env.put("topic.TOPIC", "test.topic");
> When subscribing to "sub1" I have
> env.put("topic.TOPIC", "test.topic/Subscriptions/sub1");
> The naming here seems required i.e. <<topic-name>>/Subscriptions/<
> Maybe some other naming required....or something. I will reach out to
> Azure forum also.
> I'll be back :)
> / Joacim
> On Tue, Aug 8, 2017 at 1:53 PM, Gordon Sim <g...@redhat.com> wrote:
>> On 08/08/17 12:37, Gordon Sim wrote:
>>> You could try a further experiment with another see if we can rule out
>>> one or other of these
>> E.g. if it is easy to get proton python client, you could use the
>> simple_recv.py example with -a my-namespace.servicebus.window
>> s.net:5671/test.topic and see what the protocol trace looks like with
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org