Skip to content

TP-568: Invalidate gs connections if PU starttime changes #122

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

Merged
merged 2 commits into from
Jan 17, 2022

Conversation

oskarwiksten
Copy link
Contributor

Follow-up to #121 :

  • Updates ClusteredProxyCacheImpl so that it will recreate gigaspaces connections when the latest start time of any PU has changed.
  • In particular, this change intends to address the situation where more than one astrix service binds to the same space url. In such cases, the astrix service beans were previously recreated when any PU restarted, but the gigaspaces connections remained open since the space url did not change.

* Updates `ClusteredProxyCacheImpl` so that it will recreate gigaspaces connections when the latest start time of any PU has changed.
* In particular, this change intends to address the situation where more than one astrix service binds to the same space url. In such cases, the astrix service beans were previously recreated when any PU restarted, but the gigaspaces connections remained open since the space url did not change.
@oskarwiksten oskarwiksten force-pushed the tp-568-invalidate-connection-on-pu-restart-2 branch from dc4cf2f to 849b0ef Compare January 13, 2022 06:22
* Reduce unnecessary test logging after `RestartSpaceTest`
@oskarwiksten
Copy link
Contributor Author

Thanks for review @askoog and @ath0s . Fyi, I have added a second commit onto this now that makes RestartSpaceTest clean up its threads to reduce unnecessary logging during integration tests.

@oskarwiksten oskarwiksten merged commit 71a56ee into master Jan 17, 2022
@oskarwiksten oskarwiksten deleted the tp-568-invalidate-connection-on-pu-restart-2 branch January 17, 2022 11:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants