geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Smith (JIRA)" <>
Subject [jira] [Updated] (GEODE-1687) NPE during CqStatusListener method invocation.
Date Tue, 25 Oct 2016 16:40:58 GMT


Dan Smith updated GEODE-1687:
    Fix Version/s:     (was: 2.0.0-incubating)

> NPE during CqStatusListener method invocation.
> ----------------------------------------------
>                 Key: GEODE-1687
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: cq
>            Reporter: Anilkumar Gingade
>            Assignee: Anilkumar Gingade
>             Fix For: 1.0.0-incubating.M3
> 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