geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirk Lund (JIRA)" <>
Subject [jira] [Resolved] (GEODE-1349) "java.lang.InternalError: Memory Pool not found" on client
Date Fri, 17 Jun 2016 20:28:05 GMT


Kirk Lund resolved GEODE-1349.
       Resolution: Fixed
    Fix Version/s: 1.0.0-incubating.M3

> "java.lang.InternalError: Memory Pool not found" on client
> ----------------------------------------------------------
>                 Key: GEODE-1349
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: statistics
>            Reporter: Jens Deppe
>            Assignee: Kirk Lund
>             Fix For: 1.0.0-incubating.M3
> In a client based gemfire services they got this repeating exception and cache failure:

> Caused by: java.lang.InternalError: Memory Pool not found 
> at Method) 
> at 
> at com.gemstone.gemfire.internal.stats50.VMStats50.refreshMemoryPools(

> at com.gemstone.gemfire.internal.stats50.VMStats50.refresh( 
> at com.gemstone.gemfire.internal.HostStatSampler.sampleSpecialStats(

> at 
> 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

View raw message