From issues-return-28199-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Wed May 9 16:33:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 2B4F8180674 for ; Wed, 9 May 2018 16:33:04 +0200 (CEST) Received: (qmail 27446 invoked by uid 500); 9 May 2018 14:33: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 27437 invoked by uid 99); 9 May 2018 14:33:03 -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; Wed, 09 May 2018 14:33:03 +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 CF299C00CD for ; Wed, 9 May 2018 14:33:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] 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 neNIlorxMfQn for ; Wed, 9 May 2018 14:33: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 DEA135F1E7 for ; Wed, 9 May 2018 14:33:00 +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 5B454E0047 for ; Wed, 9 May 2018 14:33: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 1F807212A1 for ; Wed, 9 May 2018 14:33:00 +0000 (UTC) Date: Wed, 9 May 2018 14:33:00 +0000 (UTC) From: "Todd Baert (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ARTEMIS-1858) Message Redistribution Sometimes Does Not Occur with AMQP Messages - "Could not find binding" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ARTEMIS-1858?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Baert updated ARTEMIS-1858: -------------------------------- Description:=20 AMQP messages that exist on node1 in a static cluster with message-redistri= bution delay of 0 are not redistributed to node2, despite the fact that nod= e2 has a matching consumer (AMQP receiver link). There is no consumer on no= de1. This issue is difficult to reproduce, most of the time the redistibuti= on/load balancing works as expected. It seems to happen more often under hi= gh load. I've seen it multiple times on a 3-node Artemis cluster with 30 ad= dresses, each with 10 consumers (10 multicast queues). The problem seems to= occur more frequently if the durable queues already exist (ie: the consume= r has connected previously). When 10 messages exist on node1,=C2=A0I see the following 10 times in the l= ogs: 2018-05-07 14:18:59,227 WARN [org.apache.activemq.artemis.core.server] AMQ2= 22196: Could not find binding with id=3D10 on routeFromCluster for message= =3DAMQPMessage [durable=3Dtrue, messageID=3D2604435, address=3DSomeAddress,= size=3D1502] binding =3D BindingsImpl [name=3DSomeAddress] See diagram below: !image-2018-05-09-10-26-43-971.png! The client in use is AMQP .Net Lite. Receiver links are created such that t= hey behave somewhat similar to a JMS2.0 shared durable subscriber: {code:java} // create a receiverlink emulating a shared durable subscriber by passing t= he capabilities below, and making it durable, and never expire ReceiverLink receiver1 =3D new ReceiverLink(session1, "receiver1", new Sour= ce(){ Address =3D "orders", Capabilities =3D new Symbol[]{"topic", "shared"= , "global"}, Durable =3D 2, ExpiryPolicy =3D new Symbol("never") }, null); {code} =C2=A0It's unclear whether the specific characteristics of this link are re= lated to the issue. was: AMQP messages that exist on node1 in a static cluster with message-redistri= bution delay of 0 are not redistributed to node2, despite the fact that nod= e2 has a matching consumer (AMQP receiver link). There is no consumer on no= de1. This issue is difficult to reproduce. It seems to happen more often un= der high load. I've seen it multiple times on a 3-node Artemis cluster with= 30 addresses, each with 10 consumers (10 multicast queues). The problem se= ems to occur more frequently if the durable queues already exist (ie: the c= onsumer has connected previously). When 10 messages exist on node1,=C2=A0I see the following 10 times in the l= ogs: 2018-05-07 14:18:59,227 WARN [org.apache.activemq.artemis.core.server] AMQ2= 22196: Could not find binding with id=3D10 on routeFromCluster for message= =3DAMQPMessage [durable=3Dtrue, messageID=3D2604435, address=3DSomeAddress,= size=3D1502] binding =3D BindingsImpl [name=3DSomeAddress] See diagram below: !image-2018-05-09-10-26-43-971.png! The client in use is AMQP .Net Lite. Receiver links are created such that t= hey behave somewhat similar to a JMS2.0 shared durable subscriber: {code:java} // create a receiverlink emulating a shared durable subscriber by passing t= he capabilities below, and making it durable, and never expire ReceiverLink receiver1 =3D new ReceiverLink(session1, "receiver1", new Sour= ce(){ Address =3D "orders", Capabilities =3D new Symbol[]{"topic", "shared"= , "global"}, Durable =3D 2, ExpiryPolicy =3D new Symbol("never") }, null); {code} =C2=A0It's unclear whether the specific characteristics of this link are re= lated to the issue. > Message Redistribution Sometimes Does Not Occur with AMQP Messages - "Cou= ld not find binding" > -------------------------------------------------------------------------= -------------------- > > Key: ARTEMIS-1858 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1858 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker > Affects Versions: 2.4.0 > Environment: RHEL, Artemis 2.4.0, AMQP .Net Lite client. > Reporter: Todd Baert > Priority: Major > Attachments: image-2018-05-09-10-21-36-439.png, image-2018-05-09-= 10-26-43-971.png > > > AMQP messages that exist on node1 in a static cluster with message-redist= ribution delay of 0 are not redistributed to node2, despite the fact that n= ode2 has a matching consumer (AMQP receiver link). There is no consumer on = node1. This issue is difficult to reproduce, most of the time the redistibu= tion/load balancing works as expected. It seems to happen more often under = high load. I've seen it multiple times on a 3-node Artemis cluster with 30 = addresses, each with 10 consumers (10 multicast queues). The problem seems = to occur more frequently if the durable queues already exist (ie: the consu= mer has connected previously). > When 10 messages exist on node1,=C2=A0I see the following 10 times in the= logs: > 2018-05-07 14:18:59,227 WARN [org.apache.activemq.artemis.core.server] AM= Q222196: Could not find binding with id=3D10 on routeFromCluster for messag= e=3DAMQPMessage [durable=3Dtrue, messageID=3D2604435, address=3DSomeAddress= , size=3D1502] binding =3D BindingsImpl [name=3DSomeAddress] > See diagram below: > !image-2018-05-09-10-26-43-971.png! > The client in use is AMQP .Net Lite. Receiver links are created such that= they behave somewhat similar to a JMS2.0 shared durable subscriber: > {code:java} > // create a receiverlink emulating a shared durable subscriber by passing= the capabilities below, and making it durable, and never expire > ReceiverLink receiver1 =3D new ReceiverLink(session1, "receiver1", new So= urce(){ Address =3D "orders", Capabilities =3D new Symbol[]{"topic", "share= d", "global"}, Durable =3D 2, ExpiryPolicy =3D new Symbol("never") }, null)= ; > {code} > =C2=A0It's unclear whether the specific characteristics of this link are = related to the issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)