[ 
https://issues.apache.org/jira/browse/GEODE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

xiaojian zhou resolved GEODE-6149.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

> when client's cache is also closing, its GetClientPRMetaDataOp could end up 
> with NPE 
> -------------------------------------------------------------------------------------
>
>                 Key: GEODE-6149
>                 URL: https://issues.apache.org/jira/browse/GEODE-6149
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: xiaojian zhou
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> {noformat}
> In some test, we hit following NPE. The root cause is, when client cache is 
> also closing, the cms.getClientPartitionAdvisor() could return null. In this 
> case, we don't have to process the PR meta data for the response. 
> Caused by: java.lang.NullPointerException
>         at 
> org.apache.geode.cache.client.internal.GetClientPRMetaDataOp$GetClientPRMetaDataOpImpl.processResponse(GetClientPRMetaDataOp.java:108)
>         at 
> org.apache.geode.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:225)
>         at 
> org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:210)
>         at 
> org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:386)
>         at 
> org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:274)
>         at 
> org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:325)
>         at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:892)
>         at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:171)
>         ... 8 more{noformat}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to