[GEODE-4100] When an unresponsive client with CQs registered gets disconnected, the onCqDisconnected callback is not invoked

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: client queues, cq
• Assignee: Unassigned
• Reporter: Barrett Oglesby
• Created: 14/Dec/17 19:09
• Updated: 14/Dec/17 19:09

Description

Neither is the onCqConnected callback invoked when the client reconnects.

QueueManagerImpl.recoverPrimary attempts to invoke the onCqConnected callback (by cqsConnected), but it is short-circuited by this check in CqServiceImpl invokeCqsConnected:

if (cqPoolsConnected.containsKey(poolName) && connected == cqPoolsConnected.get(poolName)) {
  return;
}

That check basically means the previous time this method was called, it was called with connected==true, so this call to invokeCqsConnected will succeed once QueueManagerImpl calls cqsDisconnected at the appropriate spot after the client is disconnected.