From users-return-49088-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Fri Jan 5 18:39:10 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 92CED180647 for ; Fri, 5 Jan 2018 18:39:10 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8277D160C27; Fri, 5 Jan 2018 17:39:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C8F63160C15 for ; Fri, 5 Jan 2018 18:39:09 +0100 (CET) Received: (qmail 10526 invoked by uid 500); 5 Jan 2018 17:39:08 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 10513 invoked by uid 99); 5 Jan 2018 17:39:08 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jan 2018 17:39:08 +0000 Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com [209.85.218.49]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 5EAC21A008C for ; Fri, 5 Jan 2018 17:39:08 +0000 (UTC) Received: by mail-oi0-f49.google.com with SMTP id t81so3560717oih.13 for ; Fri, 05 Jan 2018 09:39:08 -0800 (PST) X-Gm-Message-State: AKGB3mL6RUoyHZ9Iwjyf0S4kQKNkQ/LqbBkq6eOrHFeIKG7HSnfDPE8x lXVBGc9HicPaC/6DSe2+y7eo3Xem8UYoTDJZZlf3nQ== X-Google-Smtp-Source: ACJfBosJ85hyOClPeVrz7MzYSl04m+0X57hHpeHFDRvcKy3bOlsNVUDPFJxRCteO7vi+vhLDgQ5Lc/K78MLYDhgjFw8= X-Received: by 10.202.205.18 with SMTP id d18mr2076280oig.81.1515173947553; Fri, 05 Jan 2018 09:39:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.74.77.15 with HTTP; Fri, 5 Jan 2018 09:39:06 -0800 (PST) In-Reply-To: References: From: Justin Bertram Date: Fri, 5 Jan 2018 11:39:06 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Artemis: Autocreate durable queues (via AMQP) To: users@activemq.apache.org Content-Type: multipart/alternative; boundary="001a11352002ead43605620aec73" --001a11352002ead43605620aec73 Content-Type: text/plain; charset="UTF-8" If a client doesn't explicitly (e.g. via the core API, by using a configured prefix, etc.) or implicitly (e.g. working with a JMS queue (i.e. anycast) or JMS topic (i.e. multicast)) specify a routing type then the broker uses the defaults (which is multicast for both addresses and queues) when auto-creating resources. The defaults are set via the "default-address-routing-type" and "default-queue-routing-type" elements of "address-setting". You can read more about this in the documentation [1]. In your case, if you are using the defaults and you send a message to an address which doesn't exist then that address will be auto-created as multicast (i.e. the default). Multicast provides publish/subscribe semantics in Artemis and the fact that the address doesn't exist means that no subscribers care about the message you sent which means the message will be discarded. In other words, it will not be routed to any queues. If you changed the default to anycast then both an anycast address and a durable anycast queue would be created and the message would be routed to that anycast queue. Please let me know if you have additional questions. Justin [1] https://activemq.apache.org/artemis/docs/latest/address-model.html On Fri, Jan 5, 2018 at 11:04 AM, andi welchlin wrote: > Hello Justin, > > I am using the QPID Proton API (Python) and create a producer via AMQP 1.0. > I think there is no preference if it should be a queue or an exchange when > you create a producer using AMQP. > > In the code it looks like: > > > *sender = container.create_sender(self.conn, > topic_name)sender.send(amqp_message)* > > That's it. > > My idea was to define some defaults in Artemis depending on the topic name > so Artemis could autocreate a queue which is persistent. > > Kind Regards, > Andreas > > > > > > On Fri, Jan 5, 2018 at 5:40 PM, Justin Bertram > wrote: > > > Can you elaborate on your use-case a bit? What is the client doing to > > cause the queue to be auto-created (e.g. sending a message, creating a > > consumer, etc.). Is the client using the JMS API? If so, it is working > > with a "queue" or a "topic"? > > > > Also, the "name" attributes of the address and queue elements don't > support > > wild-cards. Wild-cards are supported in the "match" elements of things > > like address-setting. > > > > > > Justin > > > > On Fri, Jan 5, 2018 at 10:15 AM, andi welchlin > > wrote: > > > > > Hello, > > > > > > I would like to use queues which are automatically created. > > > > > > So I tried it out and saw that they are not durable (persistent), which > > > means a late joiner will not get messages. > > > > > > My try to configure some default behaviour for all queues which begin > > with > > > 'M' was this: > > > > > >
> > > > > > > > > true > > > > > > > > >
> > > > > > > > > But this did not work. > > > > > > Is there someone who can help me? > > > > > > Kind Regards, > > > Andreas > > > > > > --001a11352002ead43605620aec73--