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

Constant clean up required if the consumer closes abruptly #20

Open
kunalyadavdfe opened this issue Dec 14, 2016 · 2 comments
Open

Constant clean up required if the consumer closes abruptly #20

kunalyadavdfe opened this issue Dec 14, 2016 · 2 comments

Comments

@kunalyadavdfe
Copy link

SIF Consumer - "Scaleability": constant clean up required if the consumer closes abruptly. Will cause havoc when/if school turn off their servers over holiday periods.
SIF consumer application crashing or restarting without unregistering – This caused an issue where the SIF consumer was continually blocked until there was a manual clean up done of the session for that SIF consumer.

@iantasker
Copy link

This issue is linked to #19.

@drjonnicholson Am I correct in marking this as a duplicate as its related to the storage of the Session ID?

@rafidzal
Copy link
Contributor

A more robust solution needs to be investigated to manage the event whether there is inconsistent session state between a Consumer, Provider and Environment Provider. This is regardless of how storage of the session ID is managed. This is non-trivial as realistically Consumers and Providers are managed by different vendors.

joerghuber added a commit that referenced this issue Mar 6, 2018
Resolve issues with Event Consumer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants