-
Notifications
You must be signed in to change notification settings - Fork 129
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
Getting panic on otherwise successful reconnect #256
Comments
Just a follow up. It seems that there some session issues as the the MessageQueue.make_request_channel is called, but on the old session instead of the new session... I have added a uuid to the MessageQueue, for debug purpose only, to be able to track the instances.
As the I will try to get wiser on the sessions and get back. |
I fixed the panic with master...thosaa:opcua:dont-panic-on-reconnect
I was expecting the code to take up the previous subscription, what am I missing? |
FWIW: I am experiencing exactly the same problem after a reconnect (after restart of the server). |
@thosaa it looks like the code stalls because of a mutex problem at
|
The |
@locka99 is this planned to be resolved in 0.13? There seems to be several issues related to this that are fairly well hashed out and even some PRs with potential fixes. It's seems like a pretty big issue, since I imagine most people are trying to use opcua within some other application (a GUI, a web server, or whatever) and there's a pretty reasonable chance that existing application already has its own async runtime. Just trying to gauge whether the presented fixes are acceptable and will be rolled in soon, or if I should look to run a patched fork, or look for alternatives, etc. Thanks! |
I am using the current master branch and I have a problem which is very alike #243.
I get a: 'main' panicked at 'MessageQueue::send_message should never be called before make_request_channel'
Which is due to hitting the expect at: https://github.com/locka99/opcua/blob/master/lib/src/client/message_queue.rs#L57
When I unplug our real PLC from the network, wait a bit and then reconnecting the PLC I get:
The text was updated successfully, but these errors were encountered: