Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-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 76052108C4 for ; Tue, 3 Mar 2015 19:52:03 +0000 (UTC) Received: (qmail 11895 invoked by uid 500); 3 Mar 2015 19:52:02 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 11845 invoked by uid 500); 3 Mar 2015 19:52:02 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 11834 invoked by uid 99); 3 Mar 2015 19:52:02 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2015 19:52:02 +0000 Received: from mail-lb0-f178.google.com (mail-lb0-f178.google.com [209.85.217.178]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id EE70C1A0236 for ; Tue, 3 Mar 2015 19:52:01 +0000 (UTC) Received: by lbiv13 with SMTP id v13so20935550lbi.1 for ; Tue, 03 Mar 2015 11:52:00 -0800 (PST) X-Gm-Message-State: ALoCoQkuX3nBhjuzf2RaHcUKGoDdiYLsSnFmacI2GFZtMT5e5xDS7ou9v0g68kEgTnKJcKIT3+ui MIME-Version: 1.0 X-Received: by 10.112.147.104 with SMTP id tj8mr474036lbb.106.1425412320492; Tue, 03 Mar 2015 11:52:00 -0800 (PST) Received: by 10.112.17.3 with HTTP; Tue, 3 Mar 2015 11:52:00 -0800 (PST) In-Reply-To: References: Date: Tue, 3 Mar 2015 14:52:00 -0500 Message-ID: Subject: Re: Status of critical looped NPE issue? From: Camille Fournier To: "bookkeeper-user@zookeeper.apache.org" Content-Type: multipart/alternative; boundary=047d7b3a7f6a05b718051067abca --047d7b3a7f6a05b718051067abca Content-Type: text/plain; charset=UTF-8 If you're seeing it then it is an issue. I don't really know about the status of 1504, not sure if it is relevant to this directly or not but we should make sure the thing that fixes this bug is merged in whether or not 1504 is done. Thanks, C On Tue, Mar 3, 2015 at 2:48 PM, Chris Conroy wrote: > On Tue, Mar 3, 2015 at 2:36 PM, Camille Fournier > wrote: > > > Is there any more info you want to provide the ticket to help debug it in > > 3.4.6? There are some things that seem like they might be > solaris-specific. > > May of us have dev laptops with OSX so perhaps we can debug it there, > but I > > don't know how many folks have access to a solaris system to do > > system-specific debugging. > > > > I will try to get a stack trace and another sample log. I haven't been able > to reproduce it myself, but we have a lot of reports of it occurring on > OSX. > > So, I take it the issue is *not* believed to be fixed by the original patch > to the other issue? > > > > > > Thanks, > > C > > > > > > On Tue, Mar 3, 2015 at 2:22 PM, Chris Conroy > wrote: > > > > > ZOOKEEPER-1043 is a critical issue (if a > server > > > > Woops, incorrect lnk: fixed > https://issues.apache.org/jira/browse/ZOOKEEPER-1043 > > > > > gets into this state it pegs the CPU spinning in an infinite NPE loop). > > > Yet, it is unassigned and unresolved. I commented on the issue and > tried > > > asking in IRC but got no response. > > > > > > On Sep 23 2014, a comment > > > < > > > > > > https://issues.apache.org/jira/browse/ZOOKEEPER-1043?focusedCommentId=14144036&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14144036 > > > > > > > indicated > > > that another issue has been fixed and merged and that this issue may > have > > > been fixed by ZOOKEEPER-1504 > > > . However, that > > > issue > > > has been subsequently reopened. > > > > > > > > > What is the real status of this issue? > > > > > > --047d7b3a7f6a05b718051067abca--