geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anilkumar Gingade (JIRA)" <>
Subject [jira] [Resolved] (GEODE-1687) NPE during CqStatusListener method invocation.
Date Fri, 29 Jul 2016 23:23:20 GMT


Anilkumar Gingade resolved GEODE-1687.
       Resolution: Fixed
    Fix Version/s: 2.0.0-incubating

Changes checked in: 

Commit a4f93cdd634e02de13c169978e61851f810a8a32 in incubator-geode's branch refs/heads/develop
from [~agingade]
[;h=a4f93cd ]

> NPE during CqStatusListener method invocation.
> ----------------------------------------------
>                 Key: GEODE-1687
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: cq
>            Reporter: Anilkumar Gingade
>            Assignee: Anilkumar Gingade
>             Fix For: 2.0.0-incubating
> When a connection relating to CQ is established or dropped, CqStatusListner is invoked
to indicate connection/subscription status. This allows application to handle if all the subscription
connection is lost for CQs. 
> Looking at the code path for CqStatusListener there is a chance of NPE getting thrown
in CqServiceImpl.invokeCqsConnected when CQ is executed using the Bridge loader interface
(old way of client-server 
> connection)....
> When a pool or bridge-loader connection is made or dropped, the code gets all the CQs;
checks if the CQ is registered using that connection/pool name and invokes the CqStatusListner...
> The code to check if CQ is using the corresponding pool: 
> Pool cqPool = cQuery.getCQProxy().getPool();
> If the CQ is getting executed using Bridge loader, the CqProxy for CQ is not set when
its constructed; its set when it gets executed....During this time the call to cQuery.getCQProxy()
could throw NPE.

This message was sent by Atlassian JIRA

View raw message