-
Notifications
You must be signed in to change notification settings - Fork 253
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
StatusBadSessionNotActivated in updateNamespaces call during recreateSession action while reconnecting #673
Comments
Any update here? Any support would be appreciated. |
@law-dwg We're running into this issue with a couple of different servers as well. Did you ever find a resolution? I just started looking into the problem, I'll let you know if I find anything. |
…ssion. In the client.go monitor loop, the recreateSession action builds a new session on the assumption that the server is no longer holding the previous. It does not clear the value of atomicSession, which leads to CloseSession being called in ActivateSession even if there are no old sessions to be removed. This behvior was referenced in issue gopcua#673.
@law-dwg I've just released v0.5.3 with the fix from @mvandergrift. Could you please check if this also fixes the problem you were seeing? Thank you! |
Awesome, i just tested my above example, and it works flawlessly. Thanks so much @mvandergrift ! |
We are experiencing an issue with the autoreconnect functionality when trying to reestablish a connection to an OPC UA server that has been reset. In my current working example, I have a test server running out of a docker container, in which an initial connection can be established, but is unable to be reestablished when the container is restarted (docker pause seems to work fine, which makes sense since the connection is still active, just frozen)
Here is my small example:
Steps to reproduce are:
main.go
logssteps 2-4 should be completed within 60 seconds otherwise the stop duration should be changed.
The debug logs from the package seem to indicate that its stuck in a loop delivering the following messages repeatedly:
and we remain stuck in the reconnecting state (easier to see if you comment out debug flags: lines 13&14)
It looks like ActivateSession is not properly called within the recreateSession action? For reason this is the error we get when it tries to updateNamespaces.
Not sure if this is a package issue, or an issue with our server.
Any feedback would be helpful! Thanks!
The text was updated successfully, but these errors were encountered: