Correct (to my understanding).
Also another drawback is that if you have two or more subscriptions (e.g.
SUB-A and SUB-B for APP-A and APP-B) on the same topic there are no
authorization on subscription level - only on topic. So APP-A can receive
"subscribe" on SUB-B. Also missing wildcard subscriptions...we are leaning
toward RabbitMQ as of now. But experiencing some issues with Qpid JMS 0.23
with that also...
Do you know if Qpid JMS is tested to RabbitMQ?
On Thu, Aug 10, 2017 at 2:07 PM, Gordon Sim <g...@redhat.com> wrote:
> On 10/08/17 12:01, 4 Integration wrote:
>> 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
>> Bus, namely:
>> - Only one MessageProducer or MessageConsumer is allowed per Session.
>> 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
>> that use them.
>> - Transacted sessions and distributed transactions are not supported.
>> If required then need to use Azure SB API
> Just to clarify, for my own education, for topic subscriptions you need to
> set up a subscription statically and you can then use an address of the
> form <<topic-name>>/Subscriptions/<<subscription-name>> to consume from
> it, correct?
> But you cannot dynamically create subscriptions by an AMQP link attach.
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org