Log In
Home
08/31/2016
Offline
Hi,
I am currently testing our application which is an OPC client containing and running 2 different OPC UA application instances with each of them running their own session. One session is connected to a local OPC UA server (vendor A) and the other session is connected to a remote OPC UA server (with a different vendor B). What I have notice is when I restart the local server, the server state node, which I read regularly from servers, both gives a Shutdown state (even the one from the remote PC with different vendor). I don’t understand this behavior. But when I restart the remote OPC UA server (vendor B), only the session associated to it will return a shutdown, leaving the other running as it is the case and as the expected behavior.
Am I missing a configuration that suppose to make every instance or every session unique, because I use the same configuration XML to create my 2 instances? Why this behavior (multiple shutdown states on other unrelated session) when I restart the local server where my client application is?
thank you.
05/30/2017
Offline
Are you saying the the change in state of local server affects the state of the remote server?
If so you likely have a client side bug in the callback where the state change is being incorrectly handled.
If your client is .NET you can see this kind of weird behavior you have multiple event callbacks registered when you only expect one.
Using the debugger should allow you to confirm.
08/31/2016
Offline
You were right with the bug from my client configuration. I used to point on the same EndpointUrl (local) when connecting to each server. Bad file config reading (hardcoded hostname issue) from my part.
Thank you very much for your time
1 Guest(s)
Usage Policy