You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/05/13 22:18:00 UTC
[jira] [Work logged] (ARTEMIS-2614) Create queues for AMQP clients
based on FQQN
[ https://issues.apache.org/jira/browse/ARTEMIS-2614?focusedWorklogId=432869&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-432869 ]
ASF GitHub Bot logged work on ARTEMIS-2614:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/May/20 22:17
Start Date: 13/May/20 22:17
Worklog Time Spent: 10m
Work Description: Havret commented on pull request #3124:
URL: https://github.com/apache/activemq-artemis/pull/3124#issuecomment-628274586
@gemmellr I'm bringing up JMS because JMS-AMQP mapping was the first thing you referred me to. Speaking in terms of AMQP spec, words like `shared`, `global`, `topic`, and `subscription` doesn't appear there even once, and you keep bringing them up. I'm not an expert in this area, I've never spoken with the authors of the spec. The only resources I have are spec itself, Artemis Source Code, and its documentation. Forgive me my ignorance but if I read in docs for amqp connector that
> If the Terminus Durability is either UNSETTLED_STATE or CONFIGURATION then the queue will be made durable (similar to a JMS durable subscription) (...).
And I see this being used to implement JMS features I interpret it this way.
Shared Durable Subscription that you're recalling as the only feasible case to use TerminusDurability is not an AMQP feature. It's a way that JMS based clients can attach to multicast queues where topic maps to address and subscription name maps to durable queue name. The fact that the durable queue is created there is not an implementation detail from my perspective. When I configure broker I'm not configuring it in terms of topics and subscriptions. When I use FQQN I don't even need to know that such things exist. I have a broker with configured addresses and queues and I want to attach to them. In the ideal world, it would be great if it was possible to do it without the need to pre-configure (for instance to make development easier).
----------------------------------------------------------------
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
Issue Time Tracking
-------------------
Worklog Id: (was: 432869)
Time Spent: 20m (was: 10m)
> Create queues for AMQP clients based on FQQN
> --------------------------------------------
>
> Key: ARTEMIS-2614
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2614
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: AMQP
> Reporter: Krzysztof Porębski
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As a follow up to the discussion on the mailing list I would like to suggest a new feature regarding FQQN implementation for AMQP protocol - creating queues.
> Currently there is no way of attaching to a queue using FQQN if the queue is not configured upfront. It should be changed so it would be possible to create queue via FQQN and a subset of the following capabilities:
> - shared
> - topic
> - queue
--
This message was sent by Atlassian Jira
(v8.3.4#803005)