Replies: 1 comment 1 reply
-
You should be calling If that's not the issue, I'll need a self-contained example that can reproduce it. We use many simultaneous client instances and don't seem to have any issue. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have been using the sdk-client for some time with great success. Now I am setting up a system, where I need to connect with more than one connection. I have wrapped the sdk inside my own class, so all handles, callbacks etc. are unique for each connection. I use the ProSYS OPC UA Simulation server as test, and have been using the same wrapper code for both the single connect system and now the multi connect.
What I see is that my
onSessionActive
is called for the first connect, but not for the second. I tried to switch second connection to connect to the DigitalPetri test server, but I get the same result. I subscribe for data immediately afterSome very curious observations:
onSessionActive
is called for both connections when the server has started againorg.eclipse.milo.opcua.sdk.client.SessionFsm
toTRACE
, I do getonSessionActive
for both connectionsBoth connections seem to work, nodes are subscribed to, and changes on server are sent to my application. It is just the session active notification on the second connection during startup that is missing. Any idea?
This is my essential connect code (error handling etc. excluded):
The
OpcUaClient
is created in the following wayBeta Was this translation helpful? Give feedback.
All reactions