Skip to content

client: do not clear session during reconnect #534

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 1 commit into from
Jan 3, 2022

Conversation

magiconair
Copy link
Member

This patch checks if the session to be restored exists before trying to
restore it. It also prevents the internal session variable from being
cleared during a reconnect since the client would then try to restore
the session only once.

Fixes #503

This patch checks if the session to be restored exists before trying to
restore it. It also prevents the internal session variable from being
cleared during a reconnect since the client would then try to restore
the session only once.

Fixes #503
@magiconair magiconair merged commit 4e6a5a3 into main Jan 3, 2022
@magiconair magiconair deleted the issue-503-panic-on-reconnect branch January 3, 2022 12:02
@magiconair
Copy link
Member Author

this seems to have a regression. Our code fails with StatusBadSessionIDinvalid. Need to investigate.

@magiconair
Copy link
Member Author

Fixed in v0.2.6

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.

v0.2.4 and v0.2.5 fail with StatusBadSessionIDInvalid The GOPCUA client crashed when the OPCUA server was restarted?
1 participant