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

Don't revert ownership of offline sessions to the Engine in Sole Library mode #361

Closed
RichardWarburton opened this issue Apr 22, 2020 · 4 comments
Assignees

Comments

@RichardWarburton
Copy link
Contributor

No description provided.

@guoguanglei
Copy link
Contributor

guoguanglei commented Jun 1, 2020

One issue with this is we can not try to re-connect the session with that FixLibrary when Artio work as initiator.

If try to re-connect, we will receive "Duplicate Session..." because isOwnedSession in below code return true.

if (sessionContext == SessionContexts.DUPLICATE_SESSION || isOwnedSession(sessionContext.sessionId()))

Can we make the retain owner ship configurable and default to false?

Current work around is set sessionExistsHandler to AcquiringSessionExistsHandler directly instead of set InitialAcceptedSessionOwner to SOLE_LIBRARY.

@RichardWarburton
Copy link
Contributor Author

Hi Gary,

Adding more and more configuration options for different behaviors is a bit of a whack-a-mole situation. I think setting InitialAcceptedSessionOwner to SOLE_LIBRARY affecting initiating sessions is a bug. That shouldn't be the case. If a library reconnects the session and owns it then Artio should just make that work without further configuration. Happy to fix that.

Am I right in thinking that this can just be replicated by having an initiator Session connect and then disconnect and then attempt to reconnect?

@guoguanglei
Copy link
Contributor

Am I right in thinking that this can just be replicated by having an initiator Session connect and then disconnect and then attempt to reconnect?

Correct

@RichardWarburton
Copy link
Contributor Author

@guoguanglei I've pushed a fix for this. It will be in the next Artio release - hopefully today.

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

No branches or pull requests

2 participants