From issues-return-24312-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Tue Jan 9 19:49:04 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 9BC0F18072F for ; Tue, 9 Jan 2018 19:49:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8CE48160C2D; Tue, 9 Jan 2018 18:49:04 +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 D9A48160C3F for ; Tue, 9 Jan 2018 19:49:03 +0100 (CET) Received: (qmail 82096 invoked by uid 500); 9 Jan 2018 18:49:03 -0000 Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list issues@activemq.apache.org Received: (qmail 82038 invoked by uid 99); 9 Jan 2018 18:49:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jan 2018 18:49:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 62999C4312 for ; Tue, 9 Jan 2018 18:49:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.911 X-Spam-Level: X-Spam-Status: No, score=-99.911 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id jfgtUIk993MB for ; Tue, 9 Jan 2018 18:49:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 57FCF5F24E for ; Tue, 9 Jan 2018 18:49:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C483CE0662 for ; Tue, 9 Jan 2018 18:49:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 7D747212F8 for ; Tue, 9 Jan 2018 18:49:00 +0000 (UTC) Date: Tue, 9 Jan 2018 18:49:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ARTEMIS-1576) Anonymous producer with AMQP auto-creates address with wrong routing-type MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ARTEMIS-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318915#comment-16318915 ] ASF GitHub Bot commented on ARTEMIS-1576: ----------------------------------------- Github user jbertram commented on the issue: https://github.com/apache/activemq-artemis/pull/1754 I ran the PR build myself and it succeeded. It's been so long since the failure that the artifacts have been removed so I can't see why it failed originally. > Anonymous producer with AMQP auto-creates address with wrong routing-type > ------------------------------------------------------------------------- > > Key: ARTEMIS-1576 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1576 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP > Affects Versions: 2.4.0 > Reporter: Johan Stenberg > Assignee: Justin Bertram > Fix For: 2.5.0 > > Attachments: ArtemisTest.java, pom.xml > > > When publishing a message to an autocreated multicast address where no consumer is subscribed to yet, an anycast address is created. Resulting in "Address XYZ is not configured for topic support" > I tested this with the latest QPID JMS Client 0.2.8 and the latest Artemis 2.5.0-SNAPSHOT. > I attached a test class that reproduces the issue. > {noformat} > Exception in thread "main" javax.jms.JMSRuntimeException: Address topics.myTopic is not configured for topic support [condition = amqp:illegal-state] > at org.apache.qpid.jms.exceptions.JmsExceptionSupport.createRuntimeException(JmsExceptionSupport.java:207) > at org.apache.qpid.jms.JmsContext.createConsumer(JmsContext.java:314) > at ArtemisTest.main(ArtemisTest.java:93) > Caused by: javax.jms.JMSException: Address topics.myTopic is not configured for topic support [condition = amqp:illegal-state] > at org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:164) > at org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:117) > at org.apache.qpid.jms.provider.amqp.builders.AmqpResourceBuilder.handleClosed(AmqpResourceBuilder.java:185) > at org.apache.qpid.jms.provider.amqp.builders.AmqpResourceBuilder.processRemoteClose(AmqpResourceBuilder.java:129) > at org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:906) > at org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1800(AmqpProvider.java:102) > at org.apache.qpid.jms.provider.amqp.AmqpProvider$17.run(AmqpProvider.java:792) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.14#64029)