[
https://issues.apache.org/jira/browse/ARTEMIS-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025989#comment-17025989
]
Dirkjan commented on ARTEMIS-2605:
----------------------------------
Just to clarify -- it looks like Artemis does undertake queue creation on
attachment implicitly. My problem is that it seems to create a particular kind
of queue (with durable = true) which is wrong for my use case. It seems weirdly
limiting that the AMQP interface does not seemingly allow me to implicitly
create a non-durable queue whereas the Core interface does.
(Also, potentially I would be happy to write patches to get this accepted if
that helps -- and if those changes would be welcome, but because getting the
upstream project that includes Artemis to upgrade will maybe be kind of hard, a
solution that doesn't require updating Artemis would obviously make things much
easier for me.)
> Unable to create non-durable queue with specific name
> -----------------------------------------------------
>
> Key: ARTEMIS-2605
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2605
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.6.2
> Reporter: Dirkjan
> Priority: Major
>
> When attaching as a receiver to create a new queue, it appears Artemis will
> try to create a durable queue by default, even if I specify that the queue
> should not be durable. If my user does not have permission to create durable
> queues (even though it has permission to create non-durable queues), creation
> of the queue will fail with a permission error.
> More context:
> The application I'm targeting usually uses Core messages to do RPC, but it
> accepts AMQP messages as well, so it could be that there is a mismatch here
> between how things are set up.
>
> When using Core, I see that ServerSessionPacketHandler triggers on a packet
> with type -12 to create the queue with a well-defined name, which in the end
> dispatches to ServerSessionImpl.createQueue() with temporary = true and
> durable = false. This is the behavior I'm seeking to replicate. However, all
> my attempts to create to a temporary non-durable queue by attaching to it
> with AMQP seem to be failing so far.
>
> With my AMQP client, I try to create the response queue by attaching to it
> with source address = <receive-queue-name>. This lets me end up in
> ProtonServerSenderContext.initialise() by way of
> AMQPSessionContext.addSender(). However, this throws a permission error
> (AMQ119213, my user does not have permission for CREATE_DURABLE_QUEUE). This
> is surprising to me because I leave the "durable" field as default, which
> should mean to default to no durability. It seems to happen because
> AMQPSessionCallback.queueQuery() calls (through some indirection)
> ServerSessionImpl.createQueue() with durable = true.
>
> I could potentially create non-durable queues by setting dynamic = true, but
> in that case Artemis will create the queue with random UUID name, whereas my
> user only has permission to create queues with a name with a specific prefix.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
