As in a post last week:

https://groups.google.com/d/msg/rabbitmq-users/_6bD9bQDlZ0/isl651WeAQAJ

and:
"*amqp:modified:list is not currently supported by the plugin. As far as I
can see,*
*our test suite confirms this.*"



/ Joacim

On Thu, Aug 10, 2017 at 3:10 PM, 4 Integration <4integrat...@gmail.com>
wrote:

> 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?
>
> / Joacim
>
>
> 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:
>>> https://docs.microsoft.com/en-us/azure/service-bus-messaging
>>> /service-bus-java-how-to-use-jms-api-amqp#unsupported-featur
>>> es-and-restrictions
>>>
>>> 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. 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
>>> https://github.com/Azure/azure-service-bus-java
>>>
>>
>> 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
>>
>>
>

Reply via email to