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 AC3F5200CC9 for ; Mon, 17 Jul 2017 17:32:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A651D16394A; Mon, 17 Jul 2017 15:32:06 +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 ED24F163942 for ; Mon, 17 Jul 2017 17:32:05 +0200 (CEST) Received: (qmail 83871 invoked by uid 500); 17 Jul 2017 15:32:05 -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 83853 invoked by uid 99); 17 Jul 2017 15:32:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2017 15:32:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 3B9FB18071A for ; Mon, 17 Jul 2017 15:32:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.293 X-Spam-Level: **** X-Spam-Status: No, score=4.293 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 66FuAiW21daw for ; Mon, 17 Jul 2017 15:32:02 +0000 (UTC) Received: from mail-oi0-f42.google.com (mail-oi0-f42.google.com [209.85.218.42]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id B305E5FC7B for ; Mon, 17 Jul 2017 15:32:01 +0000 (UTC) Received: by mail-oi0-f42.google.com with SMTP id p188so120790029oia.0 for ; Mon, 17 Jul 2017 08:32:01 -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=6COiD3Idr1oTpCWrAxfU5tvGZOZiijWkOBeGxR26dOc=; b=hD928MeG0/tDHY3YocIMQs0Br/+rMRZ9mGn2xtQvF2v3gw0NBpTj3R5dmESpnpu+N3 5/gDsOH0ZJp+qlyL6EYvgkkKHqEGa3cwLcvtiyn1y6xyYuibuHPSxd+WLkjL4U+SxLSy zYxOIrug3SFxO40q9tlskHtUeQYOVnWHTI1xNK2ZQr0lbTuAJq6f7n3tm0IKjS17/MNa 7f1mv4gNIe88PRpXdQ+aO48gZPvoC6R1ZsaMbsdTw4NtJ1qmZDGC71llB3teUdyNviP8 g79NM29IBfz0vKHov1KLEn0Inv5TQZBjgpEJIyFO7RaHGNpBc2cmfxXU3M9/87Kl7TZR J+CA== X-Gm-Message-State: AIVw111T4OMRJH81dTs6wG8pLKnPKxHDc2bCqxR14RJFYdNgwm4dltw7 NcHbo9iJQgAAt4cFIwJEuE02h8L1KTuyggM= X-Received: by 10.202.212.65 with SMTP id l62mr14213816oig.65.1500305519210; Mon, 17 Jul 2017 08:31:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.161.19 with HTTP; Mon, 17 Jul 2017 08:31:56 -0700 (PDT) In-Reply-To: <1500302795428-4728605.post@n4.nabble.com> References: <1467059764924-4713397.post@n4.nabble.com> <1473988389349-4716576.post@n4.nabble.com> <203933147.11957835.1474032856392.JavaMail.zimbra@redhat.com> <1500302795428-4728605.post@n4.nabble.com> From: Justin Bertram Date: Mon, 17 Jul 2017 11:31:56 -0400 Message-ID: Subject: Re: [Artemis] Error message in log file for cluster on v1.3 To: users@activemq.apache.org Content-Type: multipart/alternative; boundary="001a113df3e687247c05548519fc" archived-at: Mon, 17 Jul 2017 15:32:06 -0000 --001a113df3e687247c05548519fc Content-Type: text/plain; charset="UTF-8" Do you have a reproducible test-case or anything more you could share with regards to configuration? Right now we just have some log messages and high level explanation of the configuration. That's not really enough to diagnose the problem. Justin On Mon, Jul 17, 2017 at 10:46 AM, abhijith wrote: > Resurrecting this thread as we are still facing this issue in v2.1. Any > suggestions on how to take it out? There is no issue is performance or > message delivery except filling up of logs. Its very annoying and makes > debugging almost impossible. > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Artemis-Error-message-in-log-file-for-cluster-on-v1-3- > tp4713397p4728605.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > --001a113df3e687247c05548519fc--