Return-Path: X-Original-To: apmail-logging-log4j-user-archive@www.apache.org Delivered-To: apmail-logging-log4j-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0054C19E4A for ; Mon, 21 Mar 2016 16:46:22 +0000 (UTC) Received: (qmail 7681 invoked by uid 500); 21 Mar 2016 16:46:21 -0000 Delivered-To: apmail-logging-log4j-user-archive@logging.apache.org Received: (qmail 7623 invoked by uid 500); 21 Mar 2016 16:46:21 -0000 Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Users List" Reply-To: "Log4J Users List" Delivered-To: mailing list log4j-user@logging.apache.org Received: (qmail 7612 invoked by uid 99); 21 Mar 2016 16:46:21 -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, 21 Mar 2016 16:46:21 +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 0FE6B18021D for ; Mon, 21 Mar 2016 16:46:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.002 X-Spam-Level: X-Spam-Status: No, score=-0.002 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id wJvYC0DzVnon for ; Mon, 21 Mar 2016 16:46:20 +0000 (UTC) Received: from mail-qk0-f175.google.com (mail-qk0-f175.google.com [209.85.220.175]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id E84B55F2C4 for ; Mon, 21 Mar 2016 16:46:19 +0000 (UTC) Received: by mail-qk0-f175.google.com with SMTP id p130so27680987qke.1 for ; Mon, 21 Mar 2016 09:46:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=6yOjskmj+3/dHStZ3cUXuk7jftH2sa7HIW9fx4IyztQ=; b=VVFDWAeJjY47nEQ9gEc9krTLcNAiGR5CSuOjrfZ2mdwGgn07iZegSK8x70JlasoQkm 4jeNEk+7RM6+PvG4UKdjDaZuxsAe3JcZgWDNFFCLz15Mcwigvmn/npIlMao7+zuU3EVN y0NWOH8lp7zvBXczOLvnC6fogOYGtiNwjdw09MitCInp8Q9mmut68SZ9bfSqVyMP281V y4bdFITpz3ONlcruPKE0LK9Tq++9ncNKSMh3oK5Xekq3dFhpPHIyuthlW3SyL60FLhBS W00JdwlDKR2MISpkpTXoQBFjeNWYAcLDLH5vunjhSA4UVxkXBLIyERV3XjNbNK8u9f40 cSNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=6yOjskmj+3/dHStZ3cUXuk7jftH2sa7HIW9fx4IyztQ=; b=Byh0YDVVfajWxURt7VKLSMt4yMwNgePdn/sZ7O29cxg0TvH7feu6wwRhtXBWD/QmfJ t03F/F1Hg2+uDBg5xRVo099LUaBar3SueZTzEOJ1AP1cKh/rToVGfHrZMgICutxAloEW EddVbPxyBCMXXMGq79A8VR6+BkhfLPKfwvYphVsO2QIhNhyVyxChwGIU4flsOjh5jS0V VPdy8lhg1NJoB7/sc3wsD/m9O/m+G3qnLUjmPuIUvRxZsbyy7VabN13jKCkb8GLiV9Zp KlSBeIbTEa39Xz5IQbSLSzF9DEXUCknQHOpA7z4AvxYkbcOYGXIqbiouNhhS1ovRT7WY ygtA== X-Gm-Message-State: AD7BkJKss6C0JvS4zof4hQyBzaI32DLwdKMwwotM3FqlS65oc/plS9+RRS4LH/iQiF61NEqkxnWx3KspS3mIyw== X-Received: by 10.55.71.143 with SMTP id u137mr41753324qka.1.1458578779216; Mon, 21 Mar 2016 09:46:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.86.6 with HTTP; Mon, 21 Mar 2016 09:45:59 -0700 (PDT) In-Reply-To: References: From: Ron Gonzalez Date: Mon, 21 Mar 2016 12:45:59 -0400 Message-ID: Subject: Re: Async Appender - Consumer thread dying - new thread unable to start To: Log4J Users List Content-Type: text/plain; charset=UTF-8 Opened LOG4J-1324 https://issues.apache.org/jira/browse/LOG4J2-1324 Thanks, Ron On Mon, Mar 21, 2016 at 12:31 PM, Remko Popma wrote: > I can't see any attachments. May be a mailing list restriction. Can you raise a Jira and attach the screenshot there? > Thanks! > > Sent from my iPhone > >> On 2016/03/22, at 1:05, Ron Gonzalez wrote: >> >> We are seeing a situation where the consumer thread >> "AsyncLoggerConfig-1" is apparently dying. >> We do see a new consumer thread trying to start up, but it is blocked >> waiting for a lock, so no logging is happening. >> >> Is this a defect in log4j? >> Is the original consumer thread dying due to perhaps an unhandled exception ? >> Is that original consumer thread not terminating gracefully and >> releasing the locked object so the new consumer thread can start? >> >> Please see attached screenshot. Top of screen is normal >> asyncloggerconfig thread (consumer). >> Bottom is thread trace when logging stops, we no longer see an >> "asyncloggerconfig-1" thread, instead a new thread is trying to start >> but never does "asyncloggerconfig-2". >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org >> For additional commands, e-mail: log4j-user-help@logging.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org > For additional commands, e-mail: log4j-user-help@logging.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-user-help@logging.apache.org