From issues-return-24504-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Tue Jan 16 16:07:14 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 DE51C18065B for ; Tue, 16 Jan 2018 16:07:14 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id CEDCF160C34; Tue, 16 Jan 2018 15:07:14 +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 21B9D160C26 for ; Tue, 16 Jan 2018 16:07:13 +0100 (CET) Received: (qmail 70306 invoked by uid 500); 16 Jan 2018 15:07:08 -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 70293 invoked by uid 99); 16 Jan 2018 15:07:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jan 2018 15:07:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id C50FB1A2A24 for ; Tue, 16 Jan 2018 15:07:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id zPrId1tqN4tB for ; Tue, 16 Jan 2018 15:07:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 78E9E5FBCD for ; Tue, 16 Jan 2018 15:07: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 B8B69E015F for ; Tue, 16 Jan 2018 15:07: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 7BAC5212FD for ; Tue, 16 Jan 2018 15:07:00 +0000 (UTC) Date: Tue, 16 Jan 2018 15:07:00 +0000 (UTC) From: "Christopher L. Shannon (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ARTEMIS-1610) NPE inside WildcardAddressManager on durable creation 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-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated ARTEMIS-1610: -------------------------------------------- Attachment: NPEWildcardAddressManagerTest.java > NPE inside WildcardAddressManager on durable creation > ----------------------------------------------------- > > Key: ARTEMIS-1610 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1610 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker > Affects Versions: 2.4.0 > Reporter: Christopher L. Shannon > Priority: Major > Attachments: NPEWildcardAddressManagerTest.java > > > While doing some testing with Artemis I started seeing a NPE when creating a durable subscription in certain cases. The issue occurs when there are wildcard addresses being registered/un-registered inside of the WildcardAddressManager before the creation and those addresses are linked with other addresses. This is causing the NPE inside the addBinding() method because it's trying to reference bindings that do not exist and there is no null check. I'm not sure the exact fix for this yet but I have a basic Junit test the shows the issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)