[
https://issues.apache.org/jira/browse/GEODE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977507#comment-14977507
]
ASF subversion and git services commented on GEODE-366:
-------------------------------------------------------
Commit 6d618bf821b86e2ee954492e38deed5c9032349e in incubator-geode's branch
refs/heads/feature/GEODE-409 from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=6d618bf ]
GEODE-366: Wait for clear to be propegated in ClientHealthStatsDUnitTest
The clear was showing up asynchronously on the second client. By moving
the clear up before an existing wait, it should get to the second
client before that client does a put.
> 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
> Reporter: Darrel Schneider
> Assignee: Dan Smith
> Labels: CI
>
> 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)
