You are viewing a plain text version of this content. The canonical link for it is here.
Posted to gitbox@activemq.apache.org by GitBox <gi...@apache.org> on 2020/05/24 20:24:08 UTC

[GitHub] [activemq-artemis] Havret edited a comment on pull request #3124: ARTEMIS-2614 Create queues based on FQQN for AMQP protocol

Havret edited a comment on pull request #3124:
URL: https://github.com/apache/activemq-artemis/pull/3124#issuecomment-633292814


   So the behavior shouldn't change unless somebody relies on the fact, that the broker returns an error if one tries to attach to the queue that doesn't exist, instead of simply creating it.
   
   > If i was to guess at a default queue type, i would go with a durable shared queue. You could look to make use of ParameterisedAddress like in Core to get extra queue config for a queue off the name, to allow for more configuration to be able to be present in the fqqn address
   
   I think this is the current behavior as the only difference between `createUnsharedDurableQueue` and is `createSharedDurableQueue` is that Unshared set consumer limit to 1. 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org