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 C3056200B40 for ; Fri, 17 Jun 2016 00:52:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C1A80160A52; Thu, 16 Jun 2016 22:52: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 15AAE160A51 for ; Fri, 17 Jun 2016 00:52:13 +0200 (CEST) Received: (qmail 82599 invoked by uid 500); 16 Jun 2016 22:52:08 -0000 Mailing-List: contact issues-help@geode.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.incubator.apache.org Delivered-To: mailing list issues@geode.incubator.apache.org Received: (qmail 82590 invoked by uid 99); 16 Jun 2016 22:52:08 -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; Thu, 16 Jun 2016 22:52:08 +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 D5090C1292 for ; Thu, 16 Jun 2016 22:52:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -5.446 X-Spam-Level: X-Spam-Status: No, score=-5.446 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id PoDvkbUBHJkc for ; Thu, 16 Jun 2016 22:52:07 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 523A65F297 for ; Thu, 16 Jun 2016 22:52:06 +0000 (UTC) Received: (qmail 81876 invoked by uid 99); 16 Jun 2016 22:52:05 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jun 2016 22:52:05 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 445712C0451 for ; Thu, 16 Jun 2016 22:52:05 +0000 (UTC) Date: Thu, 16 Jun 2016 22:52:05 +0000 (UTC) From: "Kirk Lund (JIRA)" To: issues@geode.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (GEODE-1349) "java.lang.InternalError: Memory Pool not found" on client MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 16 Jun 2016 22:52:14 -0000 [ https://issues.apache.org/jira/browse/GEODE-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-1349: -------------------------------- Assignee: Kirk Lund > "java.lang.InternalError: Memory Pool not found" on client > ---------------------------------------------------------- > > Key: GEODE-1349 > URL: https://issues.apache.org/jira/browse/GEODE-1349 > Project: Geode > Issue Type: Bug > Components: statistics > Reporter: Jens Deppe > Assignee: Kirk Lund > > In a client based gemfire services they got this repeating exception and cache failure: > Caused by: java.lang.InternalError: Memory Pool not found > at sun.management.MemoryPoolImpl.getUsage0(Native Method) > at sun.management.MemoryPoolImpl.getUsage(MemoryPoolImpl.java:96) > at com.gemstone.gemfire.internal.stats50.VMStats50.refreshMemoryPools(VMStats50.java:502) > at com.gemstone.gemfire.internal.stats50.VMStats50.refresh(VMStats50.java:631) > at com.gemstone.gemfire.internal.HostStatSampler.sampleSpecialStats(HostStatSampler.java:501) > at com.gemstone.gemfire.internal.HostStatSampler.run(HostStatSampler.java:195) > Unfortunately the logs have rolled and of not much use anymore. > In the code in VMStats50.refreshMemoryPools there is a check for if (!mp.isValid()) ... But there is still a time window between the MemoryPoolMXBean.isValid() call and the MemoryPoolMXBean.getUsage() call where the JVM could have gotten rid of the pool. In addition, MemoryPoolMXBean.getUsage() returns null by JVM contract and it doesn't seem the code checks for null return value. > There is no check for null value GemFire 8.x. either. > Can this and similar code paths be reviewed please? > It has happened once and after restart the issue was gone. When this happened it caused a service outage for the customer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)