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

ISPN-5150 In testing, near cache events should fire after event #3227

Closed
wants to merge 1 commit into from

Conversation

galderz
Copy link
Member

@galderz galderz commented Jan 19, 2015

  • Before this fix, events were being fired before the near cache had been updated, and as a result of that, client code was making working on assumptions that might not have yet been applied in a multi threaded environment.
  • Instead of using the Hot Rod async thread pool for client listeners, created a simple cached pool where each thread is associated with a client listener, and the thread name is adjusted when the client listener starts.
  • Added multiple TRACE log messages to help debugging.

* Before this fix, events were being fired before the near cache had
been updated, and as a result of that, client code was making working
on assumptions that might not have yet been applied in a multi threaded
environment.
* Instead of using the Hot Rod async thread pool for client listeners,
created a simple cached pool where each thread is associated with
a client listener, and the thread name is adjusted when the client
listener starts.
* Added multiple TRACE log messages to help debugging.
@tristantarrant
Copy link
Member

Pushed, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants