Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removed ListenerRegistrationHelper #11914

Closed

Conversation

ahmetmircik
Copy link
Member

@ahmetmircik ahmetmircik commented Dec 4, 2017

Fix for @vbekiaris comment [here] (#11680 (comment))

  • ListenerRegistrationHelper is removed
  • Some renamings are done

@ahmetmircik ahmetmircik added this to the 3.10 milestone Dec 4, 2017
@ahmetmircik ahmetmircik changed the title [DONT MERGE] Removed ListenerRegistrationHelper Removed ListenerRegistrationHelper Dec 5, 2017
Copy link
Contributor

@vbekiaris vbekiaris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that since this PR is altering the naming scheme for listener registrations we may have trouble with query caches on a mixed 3.9/3.10 EE cluster during an upgrade.

@@ -119,17 +115,15 @@ public String addListener(String mapName, String cacheId, MapListener listener,

@Override
public boolean removeListener(String mapName, String cacheId, String listenerId) {
String listenerName = generateListenerName(mapName, cacheId);
return eventService.deregisterListener(SERVICE_NAME, listenerName, listenerId);
return eventService.deregisterListener(SERVICE_NAME, cacheId, listenerId);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unrelated to this PR: is it OK that removeAllListeners is guarded with a mutex from lifecycleMutexFactory but removeListener is not?

@ahmetmircik ahmetmircik modified the milestones: 3.10, 4.0 Dec 5, 2017
@ahmetmircik
Copy link
Member Author

I think that since this PR is altering the naming scheme for listener registrations we may have trouble with query caches on a mixed 3.9/3.10 EE cluster during an upgrade.

@vbekiaris that's true, thanks. I set milestone to 4.0 and closing this one for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Internal PR or issue was opened by an employee Type: Enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants