Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2D027200CDA for ; Fri, 4 Aug 2017 19:40:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2970216D9CF; Fri, 4 Aug 2017 17:40:22 +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 6EDD316DBAD for ; Fri, 4 Aug 2017 19:40:21 +0200 (CEST) Received: (qmail 4462 invoked by uid 500); 4 Aug 2017 17:40:20 -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 4300 invoked by uid 99); 4 Aug 2017 17:40:18 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Aug 2017 17:40:18 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 217A4C030C for ; Fri, 4 Aug 2017 17:40:18 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.013 X-Spam-Level: * X-Spam-Status: No, score=1.013 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id X2_nI5w49qKy for ; Fri, 4 Aug 2017 17:40:15 +0000 (UTC) Received: from mail-oi0-f44.google.com (mail-oi0-f44.google.com [209.85.218.44]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 8CEF65FBCD for ; Fri, 4 Aug 2017 17:40:15 +0000 (UTC) Received: by mail-oi0-f44.google.com with SMTP id x3so21298997oia.1 for ; Fri, 04 Aug 2017 10:40:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=0fIAKTd6qVQW4AjnNh2MCHVC1Xp60XJDNLEdKCENSL0=; b=JstB7E+mxPWzffzd7PSWiF1nhAFaGfdwNArFak6JBK0c+bUceofKYbU612ThEzmBYH 0/0HKzksnhPYCpx8xR0+6Dss/UVT3EG+/UGbGwYF/B71Zy+fF8X6QtiOxBXD3Se/r4qr rVgxr+X0WmCNBcgpXmAGXEAX3gLTu18aDHeA2sJYumyN2a45rqJz1+Uh3nW9py5yvBTh pf+4oJbNGi1wf8WK738EAnO/dz4FW74Exq5cmOSvpovTg+TUTJfXVdJPf0xY3pbIRCNy PKdrzEa3uTDi4dk6L5IqnEZQ7cTk6QyEVsSk+rLLeSh1ldGGZ1TVos4eeL3gAr0gMbiY Qpxg== X-Gm-Message-State: AIVw112OgUkejt2r+FZzbxCiv6EDQ7w6x6nKANBEr18TM4iMgHBhHf1k SuQ4KqREbVthvprmn0Ai/d3/TQ6IXaLM8vU= X-Received: by 10.202.168.7 with SMTP id r7mr2498288oie.256.1501868414665; Fri, 04 Aug 2017 10:40:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.171.131 with HTTP; Fri, 4 Aug 2017 10:40:14 -0700 (PDT) In-Reply-To: <1501867561721-4729273.post@n4.nabble.com> References: <1501860307460-4729269.post@n4.nabble.com> <1501867561721-4729273.post@n4.nabble.com> From: Justin Bertram Date: Fri, 4 Aug 2017 12:40:14 -0500 Message-ID: Subject: Re: Artemis 2.2.0, createTopic create an anycast when there is no consumer created To: users@activemq.apache.org Content-Type: multipart/alternative; boundary="001a113ccff45b1ccb0555f0fd7e" archived-at: Fri, 04 Aug 2017 17:40:22 -0000 --001a113ccff45b1ccb0555f0fd7e Content-Type: text/plain; charset="UTF-8" > Is there a way to retrieve the message sent to the topic before receiver registered to the topic? No. This is basic publish-subscribe semantics. Only messages published after the subscription is created are received. Pre-creating the address with the desired routing-type is a work-around. I still think this is a bug. Justin On Fri, Aug 4, 2017 at 12:26 PM, vchen1 wrote: > Further more, I have tested the following case: > I pre-configured a topic in broker.xml: > >
> >
> > > And test the same sequence as I described earlier: > 1.) Start sender program first and send a message, and then start receiver. > There is a multicast queue created after I started receiver. However, I > couldn't located the message I send to the topic. The message count on the > newly created multicast queue is 0. Is there a way to retrieve the message > sent to the topic before receiver registered to the topic? > > 2.) Start receiver first and then start sender, now the message received > successfully. > > Thanks, > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Artemis-2-2-0-createTopic-create-an-anycast- > when-there-is-no-consumer-created-tp4729269p4729273.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > --001a113ccff45b1ccb0555f0fd7e--