You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2015/09/23 23:04:04 UTC

[jira] [Created] (GEODE-366) ClientHealthStatsDUnitTest testClientHealthStats_SubscriptionEnabled fails intermittently with NPE

Darrel Schneider created GEODE-366:
--------------------------------------

             Summary: ClientHealthStatsDUnitTest testClientHealthStats_SubscriptionEnabled fails intermittently with NPE
                 Key: GEODE-366
                 URL: https://issues.apache.org/jira/browse/GEODE-366
             Project: Geode
          Issue Type: Bug
          Components: management & tools
            Reporter: Darrel Schneider


Failed on a private build of git rev 4708d4e182f89c6a391fcad8bac854f929717685: 
{code}
at com.gemstone.gemfire.management.ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionEnabled(ClientHealthStatsDUnitTest.java:133)
[snip]
Caused by: java.lang.NullPointerException
	at com.gemstone.gemfire.management.ClientHealthStatsDUnitTest.put(ClientHealthStatsDUnitTest.java:394)
{code}
This is the code that has the NPE:
assertEquals(r1.getEntry(k1).getValue(), client_k1);

The context makes clear that r1 is not null so the NPE is caused by getEntry(k1) returning null. The line right before this did a put of k1:
r1.put(k1, client_k1);
so perhaps a concurrent destroy can happen that causes the intermittent NPE?




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)